other/10301: Side effects of architecture specific flags are not documented.

bangerth@dealii.org bangerth@dealii.org
Thu Apr 3 15:10:00 GMT 2003

Synopsis: Side effects of architecture specific flags are not documented.

Responsible-Changed-From-To: unassigned->hubicka
Responsible-Changed-By: bangerth
Responsible-Changed-When: Thu Apr  3 15:10:03 2003
    Knows best about this stuff
State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Thu Apr  3 15:10:03 2003
    To be honest, I don't find the manual all that hard to 
    understand. As to the complications you cite in your
    first link, it might be worth to also read Jan's reply to
    the linked-to mail, which gives a good reason for the
    existence of these flags. We are certainly not opposed to
    changing the docs, but maybe you could tell us what exactly
    you didn't understand in the gcc manuals?
    As to the alleged general instability of sse/... code: Jan
    has fixed lots of bugs, but in general we can only fix
    bugs that we know of. So unless people send in bug reports
    there's nothing we can do.
    With regard to disabling SSE[2]: If you don't specify some
    additional flags, sse is not used.


More information about the Gcc-bugs mailing list