1 |
Fernando Boaglio wrote: |
2 |
> Hi there! |
3 |
> |
4 |
> I was told with gcc 4.1 you can't play with some CFLAGS because you |
5 |
> will really break your system (more dangerous than gcc 3.x ! ). |
6 |
> |
7 |
> Have you tried "emerge -e system" with GCC + some uncommon flag? |
8 |
> |
9 |
> Can you share your CFLAGS with us ? |
10 |
> |
11 |
> TIA! |
12 |
> []'s |
13 |
> boaglio@×××××.com |
14 |
|
15 |
These are the flag settings I have. My WS has >2GB RAM so I'm using |
16 |
-mcmodel=medium. But as you can see, they are hardly "safe". |
17 |
|
18 |
Of the list below, the LDFLAGS -Wl,-Bdirect -Wl,-hashvals is supposed to |
19 |
make the biggest difference. I have no means of comparison. |
20 |
|
21 |
A few applications fail to compile, but so far from the >500 packages I |
22 |
currently have on my system, only the following have failed to compile |
23 |
-- glibc-2.4, gcc, sandbox, strace, transcode, libmpeg3. A few other |
24 |
applications, mainly noticed with audio applications, are behaving |
25 |
"strange". But I haven't had the opportunity to track all these problems |
26 |
down. |
27 |
|
28 |
# For GCC 4+ |
29 |
CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer -fforce-addr -ftracer |
30 |
-frename-registers -mno-tls-direct-seg-refs -mcmodel=medium" |
31 |
CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden" |
32 |
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--enable-new-dtags -Wl,-Bdirect |
33 |
-Wl,-hashvals -Wl,-zdynsort -s" |
34 |
|
35 |
# For GCC -- 3.4.5 |
36 |
#CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer -fforce-addr -ftracer |
37 |
-frename-registers" |
38 |
#CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden" |
39 |
#LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--enable-new-dtags -Wl,-zdynsort -s" |
40 |
|
41 |
# For minimal variable definitions |
42 |
#CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer" |
43 |
#CXXFLAGS="${CFLAGS}" |
44 |
#LDFLAGS="-Wl,-O1" |
45 |
|
46 |
|
47 |
Samir |
48 |
-- |
49 |
gentoo-amd64@g.o mailing list |