public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52370] [4.7/4.8/4.9 Regression] Spurious "may be used uninitialized" warning for check of optional argument
Date: Sat, 14 Dec 2013 18:18:00 -0000	[thread overview]
Message-ID: <bug-52370-4-COCHAvjBSU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52370-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-12-14
            Summary|Spurious "may be used       |[4.7/4.8/4.9 Regression]
                   |uninitialized" warning for  |Spurious "may be used
                   |check of optional argument  |uninitialized" warning for
                   |                            |check of optional argument
     Ever confirmed|0                           |1

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I get the warning with 4.6.4 up to trunk (r205944), but not for 4.5.4. The
change occurred between revisions r182107 (2011-12-08) and r182980
(2012-01-07).

> That the warning only shows up in 4.7 but not in 4.7.2 is probably due 
> to the patch for PR 50923. (The warning is only printed for -O1 but not 
> for -O2 or -O0.)

The fix for PR 50923 is in the above range.


  parent reply	other threads:[~2013-12-14 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-52370-4@http.gcc.gnu.org/bugzilla/>
2012-02-24 14:17 ` [Bug fortran/52370] " burnus at gcc dot gnu.org
2012-05-15 13:19 ` burnus at gcc dot gnu.org
2013-12-14 18:18 ` dominiq at lps dot ens.fr [this message]
2013-12-19 15:19 ` [Bug fortran/52370] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-02-11 16:21 ` jakub at gcc dot gnu.org
2014-02-11 17:31 ` jakub at gcc dot gnu.org
2014-02-11 20:49 ` [Bug fortran/52370] [4.7/4.8 " jakub at gcc dot gnu.org
2014-03-06  8:01 ` jakub at gcc dot gnu.org
2014-06-12 13:05 ` [Bug fortran/52370] [4.7 " rguenth 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-52370-4-COCHAvjBSU@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).