After writing a profiler in C#, I've now published the first of a series of articles about how use C# to... write a .NET Garbage Collector. #dotnet minidump.net/2025-28-01-w... - ThreadSky

About ThreadSky

kevingosse.net • 30 days ago

After writing a profiler in C#, I've now published the first of a series of articles about how use C# to... write a .NET Garbage Collector. #dotnet
https://minidump.net/2025-28-01-writing-a-net-gc-in-c-part-1/

Comments

migeel.sk•29 days ago

1/ Oh, this has actually two more solutions. To control what gets exported from DLLs on Windows, one needs to pass a DEF file to link.exe.

migeel.sk•29 days ago

2/ The DEF file has an EXPORTS section that describes what the DLL exports. The Native AOT compiler makes one when building a DLL. The full docs for the EXPORTS section are here: https://learn.microsoft.com/en-us/cpp/build/reference/exports?view=msvc-170

migeel.sk•29 days ago

3/ The interesting part of the doc: "If the name that you export is from some other module, specify the export's name in the DLL".

migeel.sk•29 days ago

4/ It's possible to build forwarder DLLs that simply forward to a symbol in a different DLL without writing a single line of code.

migeel.sk•29 days ago

5/ Like this:

EXPORTS
GC_Initialize=MyNativeAotDll.MyGC_Initialize

Put this in a shim.def file and run link.exe like this: `link /dll /def:shim.def /out:shim.dll /noentry`. This produces a DLL with GC_Initialize export that is forwarded to MyGC_Initialize in MyNativeAotDll.

migeel.sk•29 days ago

6/ That's possible solution one. Possible solution two involves munging the .def file that native AOT compiler creates so that we can use "If the name that you export differs from the name in the DLL, specify the export's name" from the EXPORTS docs.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply