| 1 |
You might want to add '-mtune' in addition to '-mcpu'; ia32/x86-64 gets |
| 2 |
the renamed flag in GCC 3.4. |
| 3 |
|
| 4 |
P.S. - Is your clock off by several days, or is the mailing list messing |
| 5 |
things up? I got it just now (Wed Feb 25), but it was dated Sat, 21 Feb |
| 6 |
2004 02:25:51 -0500. |
| 7 |
|
| 8 |
-- Jason Rhinelander |
| 9 |
-- Gossamer Threads, Inc. |
| 10 |
|
| 11 |
|
| 12 |
Mike Frysinger wrote: |
| 13 |
> ive just finished some updates to flag-o-matic functions so that they should |
| 14 |
> be more robust now ... however, a few flag usages in cvs are broken ... note |
| 15 |
> that they were broken before this update, i'm just giving people heads up for |
| 16 |
> future usage |
| 17 |
> |
| 18 |
> before, people used to do this: |
| 19 |
> replace-flags k6 586 |
| 20 |
> replace-flags k6-1 586 |
| 21 |
> replace-flags k6-2 586 |
| 22 |
> this was because k6 code generation was pretty bad with gcc-3.2.3 and earlier |
| 23 |
> (and i think 3.3.x has resolved most of them) |
| 24 |
> |
| 25 |
> the way replace-flags (and well, all flag-o-matic functions) is to work off of |
| 26 |
> 'flag atoms' ... that is, they dont match/replace partial flags (if they did, |
| 27 |
> this could lead to unforeseen behavior with users who use some really custom |
| 28 |
> flags) |
| 29 |
> |
| 30 |
> so, to help out in general with replacing march/mcpu flags, ive added another |
| 31 |
> function, replace-cpu-flags |
| 32 |
> replace-cpu-flags 586 k6 k6-1 k6-2 |
| 33 |
> this will replace all instances of -march=k6, -march=k6-1, and -march=k6-2 |
| 34 |
> with -march=i586 and -mcpu=k6, -mcpu=k6-1, and -march=k6-2 with -mcpu=i586 |
| 35 |
> -mike |
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives