public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-2988] Add EAF_NOREAD check to tree-ssa-uninit Date: Wed, 18 Aug 2021 11:26:57 +0000 (GMT) [thread overview] Message-ID: <20210818112657.7AAEA3857425@sourceware.org> (raw) https://gcc.gnu.org/g:e12946df34c997e96c3bc7eb5a0247e889ddb7ea commit r12-2988-ge12946df34c997e96c3bc7eb5a0247e889ddb7ea Author: Jan Hubicka <jh@suse.cz> Date: Wed Aug 18 13:25:28 2021 +0200 Add EAF_NOREAD check to tree-ssa-uninit gcc/ChangeLog: 2021-08-18 Jan Hubicka <hubicka@ucw.cz> * tree-ssa-uninit.c (maybe_warn_pass_by_reference): Check also EAF_NOREAD. Diff: --- gcc/tree-ssa-uninit.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/tree-ssa-uninit.c b/gcc/tree-ssa-uninit.c index d5cdffbae8b..ad2cf48819b 100644 --- a/gcc/tree-ssa-uninit.c +++ b/gcc/tree-ssa-uninit.c @@ -712,7 +712,7 @@ maybe_warn_pass_by_reference (gcall *stmt, wlimits &wlims) wlims.always_executed = false; /* Ignore args we are not going to read from. */ - if (gimple_call_arg_flags (stmt, argno - 1) & EAF_UNUSED) + if (gimple_call_arg_flags (stmt, argno - 1) & (EAF_UNUSED | EAF_NOREAD)) continue; tree arg = gimple_call_arg (stmt, argno - 1);
reply other threads:[~2021-08-18 11:26 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=20210818112657.7AAEA3857425@sourceware.org \ --to=hubicka@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).