public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9711: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer)
Date: Mon, 17 Feb 2003 17:16:00 -0000	[thread overview]
Message-ID: <20030217171600.9673.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/9711; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Ronald Wahl <Ronald.Wahl@informatik.tu-chemnitz.de>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: optimization/9711: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon,
 -fomit-frame-pointer)
Date: Mon, 17 Feb 2003 11:07:45 -0600 (CST)

 > Maybe we can forget all about my bug report if one could tell me if
 > it should matter if I specify march/mcpu options in cc1_options
 > instead of cc1_cpu in the spec file. If this really matters then it
 > should be documented somewhere I think. I had these options appended
 > to cc1_options. If I move'em to cc1_cpu the problems go away.
 
 I don't know anything about the spec files. However, we would certainly be 
 interested in having the piece of code that you say is miscompiled being 
 identified. If you could try to track that down, and show us how it is 
 miscompiled, that would be great!
 
 Thanks
   W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-02-17 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 17:16 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 23:06 Dara Hazeghi
2003-02-17 22:06 Wolfgang Bangerth
2003-02-17 18:36 Ronald Wahl
2003-02-15 21:46 Ronald Wahl
2003-02-14 22:15 bangerth
2003-02-14 22:06 rwahl

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=20030217171600.9673.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@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).