OSDev.org

The title says it all, can someone explain it to me? My confusions is because, LD is literally the Linker so why use GCC instead of LD?

As stated in the tutorial:

Note: Some tutorials suggest linking with i686-elf-ld rather than the compiler, however this prevents the compiler from performing various tasks during linking.

What are these 'various tasks' and how they influence in the quality of the generated binary if there's any?

AFAIK, all GCC does is invoke LD. I could be wrong, but I'm pretty sure that's what happens.

kaseiicy wrote:What are these 'various tasks' and how they influence in the quality of the generated binary if there's any?

GCC could be performing link-time optimization with the correct plugins applied. This means, essentially, that it would optimize the whole program as if everything was written into one big file. This allows the compiler to inline across file boundaries, thus eliminating more calls. The result might be a smaller or faster executable.

Other than that, the compiler also configures a few things about the linker, like adding libgcc to the command line. Finally, GCC does not call its ld directly, it calls collect2, and collect2 may actually do something.

Thx you all to explaining