From: Steve Kargl <sgk@troutmask.apl.washington.edu>
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 17:41:00 -0000 [thread overview]
Message-ID: <20050728174148.GA64356@troutmask.apl.washington.edu> (raw)
In-Reply-To: <19c433eb0507281026355950aa@mail.gmail.com>
On Thu, Jul 28, 2005 at 07:26:22PM +0200, Fran?ois-Xavier Coudert wrote:
>
> 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.
>
> How can we help here? Is there a way to make gfortran output a
> complete GIMPLE tree, that could be used for middle-end hackers to
> determine where the problem is? Or are we doomed to a dichotomy to
> know which patch caused these regressions?
>
These types of regressions have essentially halted my testing
and development on gfortran because I usually try to identify
the exact ChangeLog entry associated with the problem. This
typically involves a binary search for the problem with a
bootstrap in a clean directory for each "cvs update -D <date>".
As far as providing info to the middle-end people, you can
do -fdump-tree-all and try to sift through the volumes of
data.
--
Steve
next prev parent reply other threads:[~2005-07-28 17:41 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 [this message]
2005-07-28 22:38 ` Janis Johnson
2005-07-28 18:03 ` Daniel Berlin
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=20050728174148.GA64356@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).