| 1 |
On Friday 09 June 2006 06:46, brian@××××××××××××.com wrote: |
| 2 |
> On Fri, Jun 09, 2006 at 12:59:09AM -0300, Fernando Boaglio wrote: |
| 3 |
> > Hi there! |
| 4 |
> > |
| 5 |
> > I was told with gcc 4.1 you can't play with some CFLAGS because you |
| 6 |
> > will really break your system (more dangerous than gcc 3.x ! ). |
| 7 |
> > |
| 8 |
> > Have you tried "emerge -e system" with GCC + some uncommon flag? |
| 9 |
> > |
| 10 |
> > Can you share your CFLAGS with us ? |
| 11 |
> |
| 12 |
> Are any of these uncommon or dangerous: |
| 13 |
> |
| 14 |
> CFLAGS="-O2 -march=opteron -ffast-math -fomit-frame-pointer -mfpmath=sse |
| 15 |
> -funit- at-a-time -fpeel-loops -ftracer -funswitch-loops -pipe" |
| 16 |
> |
| 17 |
> I did a recent emerge -e world with gcc 4.1.1 and those flags. |
| 18 |
> |
| 19 |
> Haven't noticed any problems on my laptop or a workstation. |
| 20 |
> |
| 21 |
|
| 22 |
because they were filtered out. |
| 23 |
|
| 24 |
DO NEVER USE FFAST-MATH! |
| 25 |
|
| 26 |
Apps that can use it safely, usually set it in their makefile. |
| 27 |
|
| 28 |
Everything else is prone to break. |
| 29 |
|
| 30 |
And that is the reason, that almost all ebuilds have 'filter-flags' |
| 31 |
and 'strip-flags'. |
| 32 |
|
| 33 |
Again: NEVER USE IT. |
| 34 |
|
| 35 |
And: NEVER TELL ANYBODY TO USE IT. |
| 36 |
-- |
| 37 |
gentoo-amd64@g.o mailing list |
Archives