public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pme at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/11366] [3.3 regression] miscompiles XDM-AUTHORIZATION-1 key generation and/or validation in XFree86 at -O2
Date: Thu, 17 Jul 2003 02:52:00 -0000	[thread overview]
Message-ID: <20030717025256.21913.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030629091921.11366.debian-gcc@lists.debian.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11366


pme at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pme at gcc dot gnu dot org


------- Additional Comments From pme at gcc dot gnu dot org  2003-07-17 02:52 -------
Ideally, what we'd really need from the Debian team are:

1) the file that gets miscompiled, and
2) the -f flag which causes it

(1) is essential.  (2) would be nice but not crucial.  The "easy" way to
find (2) is to compile with "-fFOO" where FOO is one of the flags
turned on by -O2, as listed in the manual.  Iterate over the list until
you find the FOO that causes the breakage.  Building with "-O2 -fno-FOO"
should give you all the /other/ benefits as well as working code.

This goes much faster, of course, if you can identify (1), then you only
have to recompile that file.


  parent reply	other threads:[~2003-07-17  2:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-29  9:19 [Bug optimization/11366] New: " debian-gcc at lists dot debian dot org
2003-06-29  9:19 ` [Bug optimization/11366] " debian-gcc at lists dot debian dot org
2003-07-04 11:38 ` reichelt at gcc dot gnu dot org
2003-07-09  7:31 ` doko at cs dot tu-berlin dot de
2003-07-14 18:17 ` sirl at gcc dot gnu dot org
2003-07-14 18:44 ` james at nocrew dot org
2003-07-14 19:14 ` sirl at gcc dot gnu dot org
2003-07-15  5:46 ` doko at cs dot tu-berlin dot de
2003-07-16 16:08 ` pinskia at physics dot uc dot edu
2003-07-17  2:52 ` pme at gcc dot gnu dot org [this message]
2003-07-17  3:08 ` pinskia at physics dot uc dot edu
2003-07-20  0:46 ` mmitchel at gcc dot gnu dot org
2003-07-24 18:49 ` branden at debian dot org
2003-07-24 19:01 ` pme at gcc dot gnu dot org
2003-08-13  7:45 ` debian-gcc at lists dot debian dot org
2003-08-25  0:40 ` dhazeghi at yahoo dot com
2003-09-02  9:11 ` branden at debian dot org
2003-09-02 22:46 ` pinskia at gcc dot gnu dot org

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=20030717025256.21913.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).