Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Am I the only one...

Name: Anonymous 2005-10-22 10:12

who thinks GCC sucks? Not the compiling engine, but the interface to it. It's made of confusing, illogical, error prone options with stupid default values, and the idea of calling everyone and their mother itself (and mix everyone's options together) is as bad as penis cancer. For example, -s is passed directly to the linker, yet -rpath isn't; -Wall and most of -Wstuff controls warnings, yet -Wl is some kind of hack to pass comma-separated arguments to the linker, especially the ones not supported by gcc; etc. Whoever did this has a disturbed mind. And I think I know who did this.

Anyways, is there a sane interface which provides completely separate, non-automagical preprocessor+compiler, assembler, and linker, with well thought out options?

Name: Anonymous 2005-10-23 8:28

There are more optimizations possible, so I'm doing them.

In short, you're a ricer. Like I said, unless you're doing something unusual, using other options will get you 5% at most. march is one of the very few exceptions to this.

Runtime library search path must be set too.

LD_LIBRARY_PATH

I wanted more control over what's warned on.

Your code shouldn't emit any warnings with -Wall. Oh, it does? Fix your code.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List