From: Daniel Berlin <dberlin@dberlin.org>
To: "François-Xavier Coudert" <fxcoudert@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>, gcc@gcc.gnu.org
Subject: Re: Middle-end and optimization regressions: what should we do?
Date: Thu, 28 Jul 2005 18:03:00 -0000 [thread overview]
Message-ID: <1122573778.8038.25.camel@linux.site> (raw)
In-Reply-To: <19c433eb0507281026355950aa@mail.gmail.com>
On Thu, 2005-07-28 at 19:26 +0200, François-Xavier Coudert wrote:
> Hi all,
>
> PR 22619 and PR 22509 are two examples of recent 4.1 regressions that
> showed up in gfortran, due to middle-end or optimization bugs (only
> happen at -O3). Since these are regressions, they should be treated
> before a long time passes, but since both source codes are Fortran, I
> guess people don't (and won't) want to look at them.
I was getting these failures before my patch that added eustores, and
kenny was responsible for regtesting the tree for the ipa-* patches :)
(I always bootstrap and regtest with fortran on).
> PS: PR 22619 appeared somewhere between 20050716 and 20050717, so
> patches that could possible have messed up are:
The culprit in this case is indirectly the patch that added
ipa-reference AFAICT. -fno-ipa-reference seems to fix the bug on my
computer, see if it helps you too.
No clue why.
Given that it happens after CSE, I imagine it's enabling CSE to
eliminate something it didn't expect to be able to eliminate.
next prev parent reply other threads:[~2005-07-28 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 17:26 François-Xavier Coudert
2005-07-28 17:41 ` Steve Kargl
2005-07-28 22:38 ` Janis Johnson
2005-07-28 18:03 ` Daniel Berlin [this message]
2005-07-28 19:48 ` Andrew Pinski
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=1122573778.8038.25.camel@linux.site \
--to=dberlin@dberlin.org \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@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).