public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/13127] New: [tree-ssa] Inlining causes spurious "might be used uninitialized" warnings
Date: Wed, 19 Nov 2003 15:05:00 -0000	[thread overview]
Message-ID: <20031119150542.13127.steven@gcc.gnu.org> (raw)

While looking at Bug 13000 I noticed this bug.  Consider: 
 
static int foo (int a) { } 
int main (void) { return foo (0); } 
 
Compile this with "-O2 -Wall" and you can see that when finalizing 
`main' (after inlining foo of course), we produce this strange warning: 
 
t.i:2: warning: '({anonymous})' might be used uninitialized in this function 
 
Wtf  :-) 
 
Of course this is a regression from mainline and older GCCs. 
 
 
-------------- 
$ cat t.i 
static int foo (int a) { } 
int main (void) { return foo (0); } 
$ cc1 --version 
GNU C version 3.5-tree-ssa 20031119 (merged 20031111) (i686-pc-linux-gnu) 
        compiled by GNU C version 3.5-tree-ssa 20031119 (merged 20031111). 
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 
$ cc1 -O -Wall t.i 
 foo 
t.i: In function `foo': 
t.i:1: warning: control reaches end of non-void function 
 main 
 
$ cc1 -O2 -Wall t.i 
 main 
t.i: In function `main': 
t.i:2: warning: '({anonymous})' might be used uninitialized in this function

-- 
           Summary: [tree-ssa] Inlining causes spurious "might be used
                    uninitialized" warnings
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P2
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: steven at gcc dot gnu dot org
                CC: dnovillo at redhat dot com,gcc-bugs at gcc dot gnu dot
                    org
  GCC host triplet: any
 BugsThisDependsOn: 13000


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


             reply	other threads:[~2003-11-19 15:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 15:05 steven at gcc dot gnu dot org [this message]
2003-11-20 16:26 ` [Bug middle-end/13127] " reichelt at gcc dot gnu dot org
2003-11-20 16:31 ` bangerth at dealii dot org
2003-11-21 23:28 ` reichelt at gcc dot gnu dot org
2004-02-06  6:17 ` pinskia at gcc dot gnu dot org
2004-02-06  7:12 ` pinskia at gcc dot gnu dot org
2004-02-06 15:23 ` pinskia at gcc dot gnu dot org
2004-02-06 15:42 ` pinskia at gcc dot gnu dot org
2004-02-06 21:30 ` cvs-commit at gcc dot gnu dot org
2004-02-06 21:31 ` pinskia at gcc dot gnu dot org
2004-08-18  7:34 ` rth at gcc dot gnu dot org
2004-08-18  7:35 ` rth at gcc dot gnu dot org
2004-08-18 14:53 ` pinskia at gcc dot gnu dot org
2004-09-24  4:11 ` [Bug middle-end/13127] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-20  1:02 ` steven at gcc dot gnu dot org
2005-01-09  0:48 ` pinskia at gcc dot gnu dot org
2005-01-17  3:01 ` pinskia at gcc dot gnu dot org
2005-01-17 17:14 ` ian at airs dot com
2005-01-17 17:14 ` cvs-commit at gcc dot gnu dot org
2005-01-17 17:17 ` cvs-commit at gcc dot gnu dot 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=20031119150542.13127.steven@gcc.gnu.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).