public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56574] False possibly uninitialized variable warning
Date: Fri, 08 Mar 2013 21:26:00 -0000	[thread overview]
Message-ID: <bug-56574-4-ibgH5YUi1E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56574-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-03-08 21:25:47 UTC ---
(In reply to comment #3)
> Looking at the code that GCC generated (4.7.2 from Fedora and similarly with
> pristine 4.8 trunk@196249):



For -O2, the generated code looks though:
    testl    %edi, %edi
    sete    %dl
    testl    %eax, %eax
    setne    %al
    andl    %edx, %eax

Here eax might be uninitialized but that is ok because dl will always be 0 when
it is.


  parent reply	other threads:[~2013-03-08 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 19:10 [Bug c/56574] New: " mark.d.rustad at intel dot com
2013-03-08 19:25 ` [Bug c/56574] " mark.d.rustad at intel dot com
2013-03-08 19:51 ` [Bug middle-end/56574] " pinskia at gcc dot gnu.org
2013-03-08 21:11 ` thiago at kde dot org
2013-03-08 21:26 ` pinskia at gcc dot gnu.org [this message]
2013-03-11 10:44 ` rguenth at gcc dot gnu.org
2013-03-11 10:45 ` rguenth at gcc dot gnu.org
2014-06-06  1:06 ` luto at mit dot edu
2014-06-06  7:55 ` ebotcazou at gcc dot gnu.org
2014-06-06 12:27 ` manu at gcc dot gnu.org
2021-03-26 15:36 ` [Bug middle-end/56574] False "may be uninitialized variable" warning (&& converted to &) msebor at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2022-03-16  8:36 ` [Bug tree-optimization/56574] " coenraad at wish dot org.za
2022-03-16  8:39 ` pinskia 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-56574-4-ibgH5YUi1E@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).