public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52370] [4.7/4.8 Regression] Spurious "may be used uninitialized" warning for check of optional argument
Date: Thu, 06 Mar 2014 08:01:00 -0000	[thread overview]
Message-ID: <bug-52370-4-3ufKyMnuiy@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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Mar  6 08:00:49 2014
New Revision: 208367

URL: http://gcc.gnu.org/viewcvs?rev=208367&root=gcc&view=rev
Log:
    Backport from mainline
    2014-02-11  Jakub Jelinek  <jakub@redhat.com>

    PR fortran/52370
    * trans-decl.c (gfc_build_dummy_array_decl): Set TREE_NO_WARNING
    on decl if sym->attr.optional.

    * gfortran.dg/pr52370.f90: New test.

Added:
    branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/pr52370.f90
Modified:
    branches/gcc-4_8-branch/gcc/fortran/ChangeLog
    branches/gcc-4_8-branch/gcc/fortran/trans-decl.c
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2014-03-06  8:01 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 ` [Bug fortran/52370] [4.7/4.8/4.9 Regression] " dominiq at lps dot ens.fr
2013-12-19 15:19 ` 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 [this message]
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-3ufKyMnuiy@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).