1

While reading the Red site, I came across a statement stating that compiling an hello world Red/System program creates..

"...a 162 bytes ELF binary, while a similar C code would produce a 5-6KB binary using Gcc"

That's amazing. Can someone explain/point me to the techniques making such optimizations possible?

HostileFork says dont trust SE
  • 32,904
  • 11
  • 98
  • 167
RAbraham
  • 5,956
  • 8
  • 45
  • 80
  • 1
    I don't know the official answer, but what I do know I know from [A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux](http://www.muppetlabs.com/~breadbox/software/tiny/teensy.html) – HostileFork says dont trust SE Apr 26 '15 at 15:47

1 Answers1

1

It was achieved by having an almost empty runtime library (just a few syscalls wrappers) and an ELF emitter which would not align sections on 4K page boundaries for optimal loading.

Though, that was true for Red/System 0.1.0, so in its very early days, not true anymore (now it would be similar to other compilers). Though we still have a -r compilation option for compiling Red/System code without any runtime, but as nobody uses it, it might not work anymore (should be easy to fix anyway if someone needs it, just drop by Red's chat and ask for it. ;-))

DocKimbel
  • 3,127
  • 16
  • 27