public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ajmay81 at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53714] New: false positive for -Wuninitialized
Date: Mon, 18 Jun 2012 09:40:00 -0000	[thread overview]
Message-ID: <bug-53714-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53714
           Summary: false positive for -Wuninitialized
    Classification: Unclassified
           Product: gcc
           Version: 4.7.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ajmay81@googlemail.com


Fortran code:

      subroutine test(na,nb,nc)
      implicit none
      integer, intent(in) :: na, nb, nc
      integer ia, ib, ic, itest
      do ia=1,na
       do ib=1,nb
        do ic=1,nc
         itest=ic
        enddo
       enddo
      enddo
      do ic=1,nc
       write (6,*) ic
      enddo
      end

/opt/gcc/4.7.1/bin/gfortran -c -O1 -Wuninitialized test.f
test.f: In function ‘test’:
test.f:4:0: warning: ‘ic’ may be used uninitialized in this function
[-Wuninitialized]

Not seen with zero optimization, but for -O1 and greater the compiler reports
that 'ic' may be uninitialized.

Removing the do-loop at the end of the subroutine removes the warning, even
though it seems unrelated to the location of the alleged uninitialized case.

Removing either of the ia or ib loops (which do nothing) also removes the
warning.

Seen with 4.7.1 built from source.


             reply	other threads:[~2012-06-18  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  9:40 ajmay81 at googlemail dot com [this message]
2014-01-05 13:11 ` [Bug middle-end/53714] " dominiq at lps dot ens.fr

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