public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/30567] -fPIC -O3 optimizer bug (32-bit target only)
Date: Mon, 12 Feb 2007 00:02:00 -0000 [thread overview]
Message-ID: <20070212000235.23042.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30567-3137@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from bangerth at dealii dot org 2007-02-12 00:02 -------
(In reply to comment #6)
> I immediately believe that Andrew's and Wolfgang's findings are accurate, but I
> never claimed that the mainline has a problem. I never even tried it.
I didn't want to imply that there was no problem. It just appeared as if
neither Andrew nor I had a recent 4.2.x build around.
The person who has the infrastructure for finding regressions is Janis. Janis,
are you in a position of confirming this PR and finding where on the branch
the problem was introduced? (The PR gives pretty specific dates already.)
W.
>
> My interest it to make sure that our code works with any new gcc release, since
> that's what the OS makers pick up, and then we are stuck with the remaining
> bugs for 5+ years.
>
> It looks like a gcc 4.2 release is imminent, therefore I'm testing with the
> corresponding branch.
>
> From other bug reports I know that you have a "regression hunt" procedure. Is
> there any way I can submit my reproducer to the hunter? We have a fairly small
> time bracket already, given by Andrew's 4.2 test and the day this bug was
> opened. Therefore it would seem straightforward to find the checkin which
> caused the problem.
>
> I'll repeat my test with the current 4.2 branch and post my results here.
>
--
bangerth at dealii dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janis at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30567
next prev parent reply other threads:[~2007-02-12 0:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 0:08 [Bug c++/30567] New: " rwgk at yahoo dot com
2007-01-24 0:10 ` [Bug c++/30567] " rwgk at yahoo dot com
2007-01-24 6:57 ` pinskia at gcc dot gnu dot org
2007-01-28 20:03 ` rwgk at yahoo dot com
2007-02-03 20:42 ` rwgk at yahoo dot com
2007-02-11 4:08 ` bangerth at dealii dot org
2007-02-11 5:30 ` rwgk at yahoo dot com
2007-02-12 0:02 ` bangerth at dealii dot org [this message]
2007-02-12 5:23 ` rwgk at yahoo dot com
2007-02-12 15:48 ` rwgk at yahoo dot com
2007-02-12 16:03 ` bangerth at dealii dot org
2007-02-12 16:37 ` dberlin at gcc dot gnu dot org
2007-02-26 2:26 ` rwgk at yahoo dot com
2007-02-26 2:42 ` dberlin at dberlin dot org
2007-02-26 3:37 ` rwgk at yahoo dot com
2007-02-26 4:38 ` dberlin at gcc dot gnu dot org
2007-02-26 7:55 ` rwgk at yahoo dot com
2007-02-26 18:41 ` bangerth at dealii dot org
2007-04-18 19:00 ` hjl at lucon dot org
2007-04-18 19:02 ` hjl at lucon dot org
2007-04-18 20:47 ` hjl at lucon dot org
2007-04-18 21:11 ` [Bug c++/30567] -fPIC -O3 optimizer bug hjl at lucon dot org
2007-04-18 21:47 ` [Bug c++/30567] " rguenth at gcc dot gnu dot org
2007-04-18 21:56 ` [Bug tree-optimization/30567] " rguenth at gcc dot gnu dot org
2007-04-21 17:08 ` [Bug tree-optimization/30567] [4.2 Regression] " rguenth at gcc dot gnu dot org
2007-04-21 17:38 ` rguenth at gcc dot gnu dot org
2007-04-24 20:37 ` mmitchel at gcc dot gnu dot org
2007-04-25 2:14 ` dberlin at gcc dot gnu dot org
2007-04-25 13:22 ` rguenth at gcc dot gnu dot org
2007-04-25 13:43 ` rguenth at gcc dot gnu dot org
2007-04-25 14:04 ` rguenth at gcc dot gnu dot org
2007-04-25 15:32 ` rguenth at gcc dot gnu dot org
2007-04-25 15:42 ` rguenth at gcc dot gnu dot org
2007-04-25 16:01 ` dberlin at dberlin dot org
2007-04-25 16:13 ` rguenth at gcc dot gnu dot org
2007-04-25 18:45 ` dberlin at gcc dot gnu dot org
2007-04-26 9:02 ` rguenth at gcc dot gnu dot org
2007-04-26 11:16 ` rguenth at gcc dot gnu dot org
2007-04-26 11:16 ` rguenth at gcc dot gnu dot org
2007-04-26 15:50 ` rguenth 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=20070212000235.23042.qmail@sourceware.org \
--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).