public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at parcs dot ath.cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61112] Simple example triggers false-positive -Wmaybe-uninitialized warning
Date: Thu, 08 May 2014 14:08:00 -0000	[thread overview]
Message-ID: <bug-61112-4-UOefak0OEQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61112-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61112

--- Comment #1 from patrick at parcs dot ath.cx ---
$ gcc -O2 -Wall this.c
this.c: In function ‘void foo(int, int, int)’:
this.c:13:10: warning: ‘w’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
     p = w;
>From gcc-bugs-return-450991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 08 14:08:26 2014
Return-Path: <gcc-bugs-return-450991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17823 invoked by alias); 8 May 2014 14:08:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17791 invoked by uid 48); 8 May 2014 14:08:23 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61111] Infinite recursion between fold_build2_stat_loc and fold_binary_loc
Date: Thu, 08 May 2014 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61111-4-bIsu0uwkEB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61111-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61111-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg00683.txt.bz2
Content-length: 145

http://gcc.gnu.org/bugzilla/show_bug.cgi?ida111

--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
This is with r210212.


  reply	other threads:[~2014-05-08 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 14:07 [Bug middle-end/61112] New: " patrick at parcs dot ath.cx
2014-05-08 14:08 ` patrick at parcs dot ath.cx [this message]
2014-05-08 16:27 ` [Bug middle-end/61112] " patrick at parcs dot ath.cx
2021-03-29 19:54 ` cvs-commit at gcc dot gnu.org
2021-03-29 20:03 ` msebor at gcc dot gnu.org
2021-03-30 16:42 ` manu at gcc dot gnu.org
2021-11-30 14:44 ` aldyh 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-61112-4-UOefak0OEQ@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).