public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/68122] ICE in gcc/toplev.c:353 with -fsanitize=undefined and -fgnu-tm
Date: Wed, 28 Oct 2015 12:04:00 -0000 [thread overview]
Message-ID: <bug-68122-4-bXcVCftLo7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68122-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68122
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |trans-mem
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-10-28
Component|sanitizer |middle-end
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Looks like it doesn't handle internal function calls properly.
/* Return true if CALL is const, or tm_pure. */
static bool
is_tm_pure_call (gimple *call)
{
tree fn = gimple_call_fn (call);
if (TREE_CODE (fn) == ADDR_EXPR)
{
fn = TREE_OPERAND (fn, 0);
gcc_assert (TREE_CODE (fn) == FUNCTION_DECL);
}
else
fn will be NULL for internal functions.
next prev parent reply other threads:[~2015-10-28 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 21:41 [Bug sanitizer/68122] New: " larsbj at gullik dot net
2015-10-28 7:50 ` [Bug sanitizer/68122] " chefmax at gcc dot gnu.org
2015-10-28 12:04 ` rguenth at gcc dot gnu.org [this message]
2022-01-04 2:42 ` [Bug middle-end/68122] ICE in is_tm_pure_call " pinskia at gcc dot gnu.org
2023-11-27 8:57 ` pinskia 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-68122-4-bXcVCftLo7@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).