From: Richard Guenther <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Remove kludge in gimple_call_flags
Date: Fri, 08 Apr 2011 14:34:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1104081633410.810@zhemvz.fhfr.qr> (raw)
Now as we don't have to handle removed stmts all the time remove
this kludge.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2011-04-08 Richard Guenther <rguenther@suse.de>
* gimple.c (gimple_call_flags): Remove kludge.
Index: gcc/gimple.c
===================================================================
--- gcc/gimple.c (revision 172180)
+++ gcc/gimple.c (working copy)
@@ -1784,16 +1784,7 @@ gimple_call_flags (const_gimple stmt)
if (decl)
flags = flags_from_decl_or_type (decl);
else
- {
- tree t = TREE_TYPE (gimple_call_fn (stmt));
- /* ??? We can end up being called from gimple_set_modified from
- gsi_remove in which case the function being called can
- be a released SSA name. Give up in that case. */
- if (t)
- flags = flags_from_decl_or_type (gimple_call_fntype (stmt));
- else
- flags = 0;
- }
+ flags = flags_from_decl_or_type (gimple_call_fntype (stmt));
if (stmt->gsbase.subcode & GF_CALL_NOTHROW)
flags |= ECF_NOTHROW;
reply other threads:[~2011-04-08 14:34 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=alpine.LNX.2.00.1104081633410.810@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@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).