Never had this problem with gcc 3.3.3. I run pretty normal CFLAGS:
My suggestion to anyone else running Gentoo is to heed the warning found in several ebuilds (this one is from x11-base/xfree):
Recently there has been a lot of stability problem in Gentoo-land. Many
things can be the cause to this, but I believe that it is due to gcc3
still having issues with optimizations, or with it not filtering bad
combinations (protecting the user maybe from themselves) yet.
This can clearly be seen in large builds like glibc, where too aggressive
CFLAGS cause the tests to fail miserbly.
Quote from Nick Jones <carpaski@gentoo.org>, who in my opinion
knows what he is talking about:
Quote:
People really shouldn't force code-specific options on... It's a
bad idea. The -march options aren't just to look pretty. They enable
options that are sensible (and include sse,mmx,3dnow when apropriate).
The next command strips CFLAGS and CXXFLAGS from nearly all flags. If
you do not like it, comment it, but do not bugreport if you run into
problems.
<azarah@gentoo.org> (13 Oct 2002)