> I have noticed that there are a number of packages that > include extra code to test for and enable the -pipe > option to gcc. I think it might be a good idea to add > the -pipe option to the default CFLAGS if gcc is detected and > the -pipe option is supported. What do you think? > > It's pretty easy to write C++ code for which -pipe is slower on a > reasonable machine. Both the compiler and assembler require an > enormous amount of memory, and the system starts swapping. I've seen > this myself on a 64MB system. c++ -O2 was practically unusable for this reason before I upgraded my UltraSparc box from 64 to 128MB.
- Re: Should gcc use the -pipe option by default? Alexandre Oliva
- Re: Should gcc use the -pipe option by default? Mo DeJong
- Re: Should gcc use the -pipe option by default? Alexandre Oliva
- Re: Should gcc use the -pipe option by defau... Mo DeJong
- Re: Should gcc use the -pipe option by defau... Akim Demaille
- Re: Should gcc use the -pipe option by default? Harlan Stenn
- Re: Should gcc use the -pipe option by default? Akim Demaille
- Re: Should gcc use the -pipe option by default? Lars Hecking
- Re: Should gcc use the -pipe option by default? Marty Leisner
- Re: Should gcc use the -pipe option by default? Ian Lance Taylor
- Re: Should gcc use the -pipe option by default? Lars Hecking
- Re: Should gcc use the -pipe option by default? Mo DeJong