public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: garen@garen.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	hubicka@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: other/10301: Side effects of architecture specific flags are not documented.
Date: Thu, 03 Apr 2003 15:10:00 -0000	[thread overview]
Message-ID: <20030403151003.9236.qmail@sources.redhat.com> (raw)

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
Responsible-Changed-Why:
    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
State-Changed-Why:
    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.
    
    Regards
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10301


             reply	other threads:[~2003-04-03 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 15:10 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24 13:56 Garen
2003-04-04  0:36 Garen
2003-04-03  2:36 garen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030403151003.9236.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=garen@garen.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=hubicka@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).