From: | Alexander Skwar <listen@×××××××××××××××.name> | ||
---|---|---|---|
To: | gentoo-user-de@l.g.o | ||
Subject: | [gentoo-user-de] Re: richtigen CFLAGS für Athlon TB + regECC RAM Einstellungen | ||
Date: | Sun, 05 Sep 2004 14:51:59 | ||
Message-Id: | 413B2878.7050600@von.digitalprojects.com | ||
In Reply to: | [gentoo-user-de] richtigen CFLAGS für Athlon TB + regECC RAM Einstellungen by DonAnde |
1 | DonAnde wrote: |
2 | |
3 | > ich habe mein Server-Board von einem Duron 900 auf einen Athlon TB 1.3 + |
4 | > RAM (-> ECC reg.) upgegradet. |
5 | |
6 | > Athlon-tbird, aka K7 (AMD) |
7 | > CHOST="i686-pc-linux-gnu" |
8 | > CFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer" |
9 | > CXXFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer" |
10 | |
11 | Diesen - aber ohne -fomit-frame-pointer, da -O3 den Switch |
12 | -fomit-frame-pointer implizit beinhaltet (sowie auch -O, -O1, -O2 |
13 | und -Os). |
14 | |
15 | http://gcc.gnu.org/onlinedocs/gcc-3.3.4/gcc/Optimize-Options.html#Optimize%20Options |
16 | |
17 | Die gcc3.4.1 Doku zeigt schön was die march Flags sind: |
18 | |
19 | http://gcc.gnu.org/onlinedocs/gcc-3.4.1/gcc/i386-and-x86-64-Options.html#i386%20and%20x86-64%20Options |
20 | |
21 | Alexander Skwar |
22 | -- |
23 | I could never understand why the DEC engineers never ported DEClander to X |
24 | windows. This is totally unacceptable and definitely one of the primary causes |
25 | for VMS' demise :-) |
26 | ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ |
27 | |
28 | |
29 | -- |
30 | gentoo-user-de@g.o mailing list |
Subject | Author |
---|---|
Re: [gentoo-user-de] Re: richtigen CFLAGS für Athlon TB + regECC RAM Einstellungen | DonAnde <don.ande@×××.de> |