1 |
On Mon, Nov 28, 2011 at 2:36 PM, Pandu Poluan <pandu@××××××.info> wrote: |
2 |
> On Nov 29, 2011 2:02 AM, "Florian Philipp" <lists@×××××××××××.net> wrote: |
3 |
>> Am 28.11.2011 18:56, schrieb Michael Mol: |
4 |
>> > On Mon, Nov 28, 2011 at 11:46 AM, Pandu Poluan <pandu@××××××.info> |
5 |
>> > wrote: |
6 |
>> >> On Nov 28, 2011 10:38 PM, "Michael Mol" <mikemol@×××××.com> wrote: |
7 |
>> >>> On Sun, Nov 27, 2011 at 7:54 PM, Pandu Poluan <pandu@××××××.info> |
8 |
>> >>> wrote: |
9 |
>> >>>> Won't file a bug report, though. I have a feeling that my bug report |
10 |
>> >>>> re: |
11 |
>> >>>> emerge failure will be marked WONTFIX thanks to the 'ricer special' |
12 |
>> >>>> CFLAGS |
13 |
>> >>> |
14 |
>> >>> The CFLAGS you showed me weren't any more ricer than "-O2 |
15 |
>> >>> -march=native". (I didn't know that -D_FORTIFY=2 came from gcc) |
16 |
>> >>> |
17 |
>> >>> They wouldn't have a leg to stand on... |
18 |
>> >>> |
19 |
>> >> |
20 |
>> >> Mine is: |
21 |
>> >> |
22 |
>> >> CFLAGS="-O2 -march=native -fomit-frame-pointer -floop-interchange |
23 |
>> >> -floop-strip-mine -floop-block -funsafe-math-optimizations |
24 |
>> >> -fexcess-precision=fast" |
25 |
>> >> |
26 |
>> >> If you tell me that's not a ricer's CFLAGS, then you've just made me a |
27 |
>> >> very |
28 |
>> >> happy cat :-) |
29 |
>> > |
30 |
>> > No, you've got some ugly flags in there. -fexcess-precision and |
31 |
>> > -funsafe-math-optimizations, in particular. (I must have been talking |
32 |
>> > to someone else last week; sorry, I'm terrible with names.) |
33 |
>> > |
34 |
>> |
35 |
>> I doubt -fexcess-precision=fast does anything at all. Pandu uses an |
36 |
>> AMD64 system, right? Then you have -mfpmath=sse set per default and SSE |
37 |
>> does not have excess precision issues (that's just for the old x87 FPU). |
38 |
> |
39 |
> I use Intel boxes, unfortunately. |
40 |
|
41 |
Are you using a 64-bit x86-derived system? Same difference in this |
42 |
context. AMD hit the market with a good 64-bit x86-based ISA first, |
43 |
and devs started calling it AMD64 then. That's mostly stuck even after |
44 |
Intel released a mostly-compatible competitor, EM64T. |
45 |
|
46 |
-- |
47 |
:wq |