public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/54540] postreload incorrectly simplifies stack adjustment into constant load into SP
Date: Tue, 20 Nov 2012 11:09:00 -0000 [thread overview]
Message-ID: <bug-54540-4-QnarIXTxI5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54540-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54540
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
--- Comment #7 from Steven Bosscher <steven at gcc dot gnu.org> 2012-11-20 11:09:12 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > Can this be closed now?
>
> Well the comment 4 is still relevant, I suspect that there are still latent
> issues in postreload.
Are we going to keep a bug report open because of a _suspected_ bug, with
no test case to reproduce the problem with the current trunk? Any new bug
report without a test case would be almost immediately closed as INVALID,
and I see no good reason to do things differently for an existing PR with
a fix applied and no test case remaining to reproduce the issue.
Have you at least looked at postreload (using a compiler without your fix
for reload) to see where things go bad? I suspect the bad insn is created
in reload_combine_recognize_pattern. You could try to rule out move2add
using debug counters (-fdbg-cnt=cse2_move2add:0) at least.
next prev parent reply other threads:[~2012-11-20 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 11:04 [Bug rtl-optimization/54540] New: [4.8 regression] " rearnsha at gcc dot gnu.org
2012-09-10 11:54 ` [Bug rtl-optimization/54540] " rguenth at gcc dot gnu.org
2012-09-10 12:46 ` rearnsha at gcc dot gnu.org
2012-09-10 13:53 ` segher at gcc dot gnu.org
2012-09-14 17:11 ` rearnsha at gcc dot gnu.org
2012-09-15 9:57 ` rearnsha at gcc dot gnu.org
2012-11-20 9:27 ` jakub at gcc dot gnu.org
2012-11-20 9:35 ` rearnsha at gcc dot gnu.org
2012-11-20 11:09 ` steven at gcc dot gnu.org [this message]
2013-03-22 14:47 ` [Bug rtl-optimization/54540] " jakub at gcc dot gnu.org
2013-05-31 11:00 ` jakub at gcc dot gnu.org
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2015-06-22 14:26 ` rguenth at gcc dot gnu.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=bug-54540-4-QnarIXTxI5@http.gcc.gnu.org/bugzilla/ \
--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).