public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28200] One warning seems to appear only with '-O2' even though '-Wall' is specified
Date: Thu, 29 Jun 2006 13:09:00 -0000	[thread overview]
Message-ID: <20060629125520.12022.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28200-10601@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from pinskia at gcc dot gnu dot org  2006-06-29 12:55 -------
Please read
http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#Warning-Options:
-Wuninitialized
Warn if an automatic variable is used without first being initialized or if a
variable may be clobbered by a setjmp call.
These warnings are possible only in optimizing compilation, because they
require data flow information that is computed only when optimizing. If you do
not specify -O, you will not get these warnings. Instead, GCC will issue a
warning about -Wuninitialized requiring -O.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


      reply	other threads:[~2006-06-29 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 11:42 [Bug fortran/28200] New: " P dot Schaffnit at access dot rwth-aachen dot de
2006-06-29 13:09 ` pinskia at gcc dot gnu dot org [this message]

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=20060629125520.12022.qmail@sourceware.org \
    --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).