#
+# Decent examples:
+#
-+#CFLAGS="-mcpu=ev67 -O3 -pipe "
-+CFLAGS="-mcpu=ev5 -O3 -pipe "
++#CFLAGS="-mcpu=ev67 -O2 -pipe "
++CFLAGS="-mcpu=ev5 -O2 -pipe "
+
# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
+# example, -march=xscale code will not run on a StrongARM 11x0, and
+# -march=strongarm110 code will not run on a regular StrongARM).
+#
-+# Don't use -O3. Even -O2 may be risky in some cases.
++# Don't use -O2. Even -O2 may be risky in some cases.
+#
+# For a full listing of supported CPU models, please refer to the GCC website:
+# http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/ARM-Options.html
+#
+# The newer gcc has a stricter aliasing ruleset that makes type punned
+# expression faulty compiled if -fstrict-aliasing is enabled.
-+# That option is implied by -O2 -Os and -O3. Make SURE you don't have that
++# That option is implied by -O2 -Os and -O2. Make SURE you don't have that
+# option enabled by adding -fno-strict-aliasing to your CFLAGS and CXXFLAGS
+#
-+# Long term testing has shown that -O3 opts can be unreliable on G4's but work
++# Long term testing has shown that -O2 opts can be unreliable on G4's but work
+# on G3 series processors or earlier.
+#
+# The following is the suggested CFLAGS for a generic G4 cpu
+# all G3 and pre machines. (note it will not hurt pre G3 machines either to
+# use this mcpu option as it is the default for gcc 3.2.x anyway)
+#
-+#CFLAGS="-O3 -pipe -mcpu=G3 -fno-strict-aliasing"
++#CFLAGS="-O2 -pipe -mcpu=G3 -fno-strict-aliasing"
+
+# Recommended settings for GCC 2.95.3 only (Gentoo 1.2 or older):
+#
+# feature. Note: you should also include -mabi=altivec flag if using this option.
#
-#CFLAGS="-O2 -pipe"
-+# -O3 for the most part seems ok but should be used with caution as
++# -O2 for the most part seems ok but should be used with caution as
+# for instance app-editors/vim has problems if it is used. -O2 is a
+# good selection.
+#
+# your CHOST so if you are using "sh4-unknown-linux-gnu", you should have
+# -m4 below.
#
-+# Don't use -O3. Even -O2 may be risky in some cases.
++# Don't use -O2. Even -O2 may be risky in some cases.
+#
+# For a full listing of supported CPU models, please refer to the GCC website:
+# http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/SH-Options.html
+#
+# Decent examples:
+#
-+#CFLAGS="-mcpu=supersparc -O3 -pipe"
-+#CFLAGS="-mcpu=ultrasparc -O3 -pipe"
++#CFLAGS="-mcpu=supersparc -O2 -pipe"
++#CFLAGS="-mcpu=ultrasparc -O2 -pipe"
+#CFLAGS="-mcpu=v8 -mtune=v9 -O2 -pipe"
+
# If you set a CFLAGS above, then this line will set your default C++ flags to
#
+# Decent examples:
+#
-+#CFLAGS="-mtune=athlon-xp -O3 -pipe"
-+#CFLAGS="-march=pentium3 -O3 -pipe"
++#CFLAGS="-mtune=athlon-xp -O2 -pipe"
++#CFLAGS="-march=pentium3 -O2 -pipe"
+
# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
+# NOTE: the -On optimization levels are set with the letter O, not -0 (zero).
+#
+# Decent examples:
-+#CFLAGS="-mcpu=athlon-xp -O3 -pipe"
-+#CFLAGS="-march=pentium3 -O3 -pipe"
++#CFLAGS="-mcpu=athlon-xp -O2 -pipe"
++#CFLAGS="-march=pentium3 -O2 -pipe"
+
# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
projects / portage.git / commitdiff