public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/strub)] strub type checking Date: Wed, 4 Aug 2021 09:04:34 +0000 (GMT) [thread overview] Message-ID: <20210804090434.066783971C38@sourceware.org> (raw) https://gcc.gnu.org/g:396d2d0536e89b78ace8ce2f806031e8dfcdcb35 commit 396d2d0536e89b78ace8ce2f806031e8dfcdcb35 Author: Alexandre Oliva <oliva@gnu.org> Date: Wed Aug 4 05:52:43 2021 -0300 strub type checking Diff: --- gcc/ipa-strub.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gcc/ipa-strub.c b/gcc/ipa-strub.c index e302f0ec1c5..81d961ac44e 100644 --- a/gcc/ipa-strub.c +++ b/gcc/ipa-strub.c @@ -429,12 +429,12 @@ can_strub_internally_p (cgraph_node *node, bool report = false) node->decl); } - if (result) - /* Since we're not changing the function identity proper, just - moving its full implementation, we *could* disable - fun->cannot_be_copied_reason and/or temporarily drop a noclone - attribute. */ - gcc_checking_assert (tree_versionable_function_p (node->decl)); + /* Since we're not changing the function identity proper, just + moving its full implementation, we *could* disable + fun->cannot_be_copied_reason and/or temporarily drop a noclone + attribute. */ + gcc_checking_assert (!result || !node->has_gimple_body_p () + || tree_versionable_function_p (node->decl)); return result; }
next reply other threads:[~2021-08-04 9:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 9:04 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-08-04 12:46 Alexandre Oliva 2021-08-04 8:55 Alexandre Oliva
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=20210804090434.066783971C38@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).