From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>, gcc@gcc.gnu.org
Subject: Re: GCC-3.3.4 release status report
Date: Tue, 30 Mar 2004 00:24:00 -0000 [thread overview]
Message-ID: <40689033.6070206@tat.physik.uni-tuebingen.de> (raw)
In-Reply-To: <20040329091650.B32489@synopsys.com>
Joe Buck wrote:
> On Sat, Mar 27, 2004 at 11:09:52AM +0100, Gabriel Dos Reis wrote:
>
>> The number of open PRs targetted for 3.3.4 has grown up to 46
>>(from 41 last report).
>>
>> Some PRs have been fixed, others are new.
>>The set of critical PRs is now 8 and is different from what we got
>>last report:
>>
> ([3.3 regression] -O2 -funroll-loop miscompiles POOMA testcase)
>
> Now *this* is one that I'd like to see fixed! It's likely to be tractable
> because 3.2.3 worked, and it's nasty.
I'm the reporter of the bug (and there is another arch-specific for
powerpc, maybe related, PR13222), and the bug looks indeed serious. But
I personally am using already 3.4 for production use and tree-ssa for
testing - and POOMA based testcases are huge - even if this one was
reduced a lot already. Someone with good understanding of the loop
unroller and rtl needs to look at this. At least warn about use of
-funroll-loops as it caused that many regressions in the past.
One problem is that we don't excercise those commonly (in scientific
apps) used options in any -O level, so this gets too less beating on in
regular C apps which would result in so much nicer testcases...
So, in conclusion, I'd be not too unhappy if this is _not_ fixed for 3.3.4.
>> optimization/11841
>
>
> Likewise this one; could be related to 13653 (another -funroll-loop bug
> new since 3.2.3)
Let's hope fixing one of 11841, 13222 or 13653 fixes the other cases.
Or simply strip off handling of "unusual" cases from the unroller and
rather pessimize the odd cases than producing wrong code.
Richard.
next prev parent reply other threads:[~2004-03-29 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 21:26 Gabriel Dos Reis
2004-03-29 19:17 ` Joe Buck
2004-03-30 0:24 ` Richard Guenther [this message]
2004-03-30 18:46 ` Gabriel Dos Reis
2004-03-31 1:15 ` Joe Buck
2004-03-30 0:20 Wolfgang Bangerth
2004-03-30 18:56 ` Gabriel Dos Reis
2004-03-30 19:19 ` Theodore Papadopoulo
2004-03-30 23:59 ` Joe Buck
2004-03-31 2:50 ` Eric Botcazou
2004-03-31 3:10 ` Daniel Berlin
2004-03-31 11:24 ` Eric Botcazou
2004-03-31 12:42 ` Gabriel Dos Reis
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=40689033.6070206@tat.physik.uni-tuebingen.de \
--to=rguenth@tat.physik.uni-tuebingen.de \
--cc=Joe.Buck@synopsys.COM \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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).