as per $summary, with + o - custom-optimization/custom-cflags, the buildsystem adds itself -pipe and add itself also -g with USE="-debug" small example from log: x86_64-pc-linux-gnu-g++ -o nsConsoleService.o -c -I../../dist/stl_wrappers -I../../dist/system_wrappers -include ../../config/gcc_hidden.h -DXP_LINUX -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API -D_IMPL_NS_GFX -D_IMPL_NS_WIDGET -DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES -DSTATIC_EXPORTABLE_JS_API -DMOZ_THUNDERBIRD=1 -DOSTYPE=\"Linux2.6\" -DOSARCH=Linux -D_IMPL_NS_COM -I./../build -I. -I. -I../../dist/include -I../../dist/include/nsprpub -I/usr/include/nspr -I/usr/include/nss -fPIC -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -march=native -Wno-return-type -w -mno-avx -fno-strict-aliasing -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/gtk-unix-print-2.0 -DMOZILLA_CLIENT -include ../../mozilla-config.h -MD -MF .deps/nsConsoleService.pp nsConsoleService.cpp
same thing for firefox-5.0-r2
Adding -pipe is fine, but adding -g is a problem.
(In reply to comment #2) > Adding -pipe is fine Not all fine, it increases the dimension of code at build time, if user wants, adds it in his make.conf ;)
(In reply to comment #3) > (In reply to comment #2) > > Adding -pipe is fine > > Not all fine, it increases the dimension of code at build time, if user wants, > adds it in his make.conf ;) What do you mean by dimension of code? -pipe only causes gcc to pipe data instead of writing temporary files. It is pretty much always faster. I know of no reason to not enable it.
(In reply to comment #4) > -pipe only causes gcc to pipe data instead of writing temporary files. It is > pretty much always faster. I know of no reason to not enable it. Is not advised for system with short ram, I repeate, if you want, add it to your make.conf but it shouldn't be enabled for all From: http://www.gentoo.org/doc/en/gcc-optimization.xml It tells the compiler to use pipes instead of temporary files during the different stages of compilation(as you sayd), which uses *more* memory. On systems with low memory, gcc might get killed. In that case, do not use this flag.
If any can be duplicated or reproduce feel free to update summary and reopen please.
