News for hackers. Stuff that matters.

A comment on Introducing .NET IL Linker. Parent comment

Re:Introducing .NET IL Linker by algorithmsRcool on Wednesday August 30, 2017 @03:42PM (#15135280)
Put another way: what should be left after linking is just the parts of the CLR + BCL that the runtime needs to function. Apparently that takes 12MB today. There is a JIT, GC and Execution Engine all in there.

The number might shrink as the linker gets more aggressive but i wouldn't count on it much.

The application IL code is perhaps 50 bytes to for hello world.

[ Parent | on HN ]
Re:Introducing .NET IL Linker by Kuraj on Wednesday August 30, 2017 @03:50PM (#15135355)
12 megabytes doesn't sound too bad for the things you mentioned, especially if it's a constant cost.
[ Parent | on HN ]
Re:Introducing .NET IL Linker by svick on Friday September 01, 2017 @06:10PM (#15152764)
> The application IL code is perhaps 50 bytes to for hello world.

A Hello World assembly in .Net Core 2.0 is 4.5 kB.

Out of that, the IL is 11 bytes, though that doesn't even include the "Hello world!" string.

[ Parent | on HN ]