public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/101902] [12 regression] g++.dg/warn/uninit-1.C has excess errors after r12-2898
Date: Tue, 07 Sep 2021 01:03:18 +0000	[thread overview]
Message-ID: <bug-101902-4-ZqFQZ7UBOX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101902-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101902

Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #1)
> Hi,
> i am testing
> 
> diff --git a/gcc/tree-ssa-uninit.c b/gcc/tree-ssa-uninit.c
> index 5d7bc800419..d89ab5423cd 100644
> --- a/gcc/tree-ssa-uninit.c
> +++ b/gcc/tree-ssa-uninit.c
> @@ -641,7 +641,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);

Looks like Jan committed this as e12946df34c997e96c3bc7eb5a0247e889ddb7ea but
forgot to mark the commit-log.  I'm closing this.

      parent reply	other threads:[~2021-09-07  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 15:47 [Bug testsuite/101902] New: " seurer at gcc dot gnu.org
2021-08-16  5:30 ` [Bug testsuite/101902] " hubicka at ucw dot cz
2021-08-16  7:58 ` marxin at gcc dot gnu.org
2021-08-16  9:00 ` rguenth at gcc dot gnu.org
2021-09-07  1:03 ` hp at gcc dot gnu.org [this message]

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-101902-4-ZqFQZ7UBOX@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).