public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "terry.guo at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64815] ICE caused by volatile_refs_p doesn't skip NULL operand
Date: Tue, 27 Jan 2015 06:43:00 -0000 [thread overview]
Message-ID: <bug-64815-4-Hui2Mt3igZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64815-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
--- Comment #2 from Terry Guo <terry.guo at arm dot com> ---
(In reply to Andrew Pinski from comment #1)
> I don't think you need to call volatile_refs_p on the notes part of the
> instruciton.
The volatile_refs_p works in a recursive way which makes itself to scan the
notes part. I just call volatile_refs_p to the insn.
Do you mean I should update volatile_refs_p to avoid recursively scanning the
notes part of the insn?
next prev parent reply other threads:[~2015-01-27 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 5:59 [Bug rtl-optimization/64815] New: " terry.guo at arm dot com
2015-01-27 6:09 ` [Bug rtl-optimization/64815] " pinskia at gcc dot gnu.org
2015-01-27 6:43 ` terry.guo at arm dot com [this message]
2015-01-27 6:57 ` pinskia at gcc dot gnu.org
2015-01-27 6:58 ` pinskia at gcc dot gnu.org
2015-01-27 7:47 ` terry.guo at arm dot com
2015-01-28 1:53 ` terry.guo at arm dot com
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-64815-4-Hui2Mt3igZ@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).