

Code: Select all
USE="3dnow enlightenment ethereal fb fbcon fbdev freetype \
freetype-version-1 galeon glut gtk2 mail netkit-fingerd netkit-rsh \
netkit-tftp nocardbus nowin nslookup nvidia offensive parse-clocks \
radeon src sse type1 usb wavelan yp-tools -apm -arts -cups -kde \
-gnome -quicktime -gdbm -berkdb -gpm"
Code: Select all
CFLAGS="-march=athlon-mp -O3 -finline-functions -fomit-frame-pointer -pipe -fforce-addr -funroll-loops -frerun-loop-opt -frerun-cse-after-loop -falign-functions=4 -fexpensive-optimizations -falign-jumps=4 -ffast-math -mmmx -msse -fprefetch-loop-arrays -mfpmath=sse"

Of course CFLAGS are a placebo. But - when measured, they have a slight effect too.-00, -01, -02, -03
Forces GCC to halt with a fatal error, immediately.


Mystilleef wrote:You need to be cautious with which flags you use. As a rule, don't use flags for which you don't know it's function or effect. Many of them have catastrophic side effects.
Code: Select all
emerge -eD worldYou put the flags in your make.conf after CFLAGS=darkie_ wrote:with a risk of sounding stupid, but when do you put these flags? is it when your compiling the kernel or when is it?
and what does the different flags mean? like this -03 that is directly after what processor you have?

