From: "Bin.Cheng" <amker.cheng@gmail.com>
To: gcc@gcc.gnu.org
Subject: Bug in reload when forming inheritable reload information?
Date: Tue, 03 Apr 2012 17:02:00 -0000 [thread overview]
Message-ID: <CAHFci28KXn24UMkg6d5VrLmEyAyXX21pqYmtUdVL0j-vqWSOKQ@mail.gmail.com> (raw)
Hi,
Recently I found a test program got wrongly reloaded, as reported in PR52804.
As the comment, I think reload_reg_reaches_end_p in reload1.c should
handle case:
The first reload type is RELOAD_FOR_INPADDR_ADDRESS;
the second reload type is RELOAD_FOR_INPADDR_ADDRESS and the reload
register is same as the first one.
In this case, the first reload is corrupted by the second one, but for now
reload_reg_reaches_end_p still returns 1, resulting in forming wrong
inheritable information,
then mis-leading following instructions.
I am working/testing a patch for this right now, also I'd like to get
some confirmation on this issue,
because RELOAD is a well-known complicated pass.
Any comments? Thanks very much.
--
Best Regards.
reply other threads:[~2012-04-03 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHFci28KXn24UMkg6d5VrLmEyAyXX21pqYmtUdVL0j-vqWSOKQ@mail.gmail.com \
--to=amker.cheng@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).