public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47837] New: FAIL: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 26)
Date: Mon, 21 Feb 2011 15:06:00 -0000 [thread overview]
Message-ID: <bug-47837-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47837
Summary: FAIL: gcc.dg/uninit-pred-7_a.c bogus warning (test for
bogus messages, line 26)
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: danglin@gcc.gnu.org
Host: hppa1.1-hp-hpux10.20
Target: hppa1.1-hp-hpux10.20
Build: hppa1.1-hp-hpux10.20
Executing on host: /xxx/gnu/gcc/objdir/gcc/xgcc -B/xxx/gnu/gcc/objdir/gcc/
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c -Wuninitialized -O2
-S -o
uninit-pred-7_a.s (timeout = 300)
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c: In function
'foo':/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c:26:11: warning:
'v' may
be used uninitialized in this function [-Wuninitialized]
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c: In function 'foo_2':
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c:48:12: warning: 'v' may
be used uninitialized in this function [-Wuninitialized]
output is:
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c: In function
'foo':/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c:26:11: warning:
'v' may
be used uninitialized in this function [-Wuninitialized]
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c: In function 'foo_2':
/xxx/gnu/gcc/gcc/gcc/testsuite/gcc.dg/uninit-pred-7_a.c:48:12: warning: 'v' may
be used uninitialized in this function [-Wuninitialized]
PASS: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 20)
PASS: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 23)
FAIL: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 26)
PASS: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 42)
PASS: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 45)
PASS: gcc.dg/uninit-pred-7_a.c warning (test for warnings, line 48)
PASS: gcc.dg/uninit-pred-7_a.c bogus warning (test for bogus messages, line 51)
PASS: gcc.dg/uninit-pred-7_a.c (test for excess errors)
next reply other threads:[~2011-02-21 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:06 danglin at gcc dot gnu.org [this message]
2011-03-03 12:43 ` [Bug c/47837] " krebbel at gcc dot gnu.org
2011-03-03 17:32 ` xinliangli at gmail dot com
2011-03-03 17:39 ` krebbel at gcc dot gnu.org
2011-03-03 17:39 ` krebbel at gcc dot gnu.org
2011-03-03 18:06 ` xinliangli at gmail dot com
2011-03-03 18:37 ` pinskia at gcc dot gnu.org
2011-03-07 8:40 ` xinliangli at gmail dot com
2011-03-07 8:42 ` xinliangli at gmail dot com
2011-03-07 11:48 ` krebbel at gcc dot gnu.org
2011-03-07 16:00 ` krebbel at gcc dot gnu.org
2011-03-07 16:01 ` krebbel at gcc dot gnu.org
2011-03-07 16:01 ` krebbel at gcc dot gnu.org
2011-03-07 16:58 ` xinliangli at gmail dot com
2011-03-07 18:59 ` mikpe at it dot uu.se
2011-03-08 0:25 ` xinliangli at gmail dot com
2011-03-08 0:27 ` xinliangli at gmail dot com
2011-03-08 11:08 ` mikpe at it dot uu.se
2011-03-08 14:40 ` krebbel at gcc dot gnu.org
2015-10-22 9:43 ` mpolacek 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-47837-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).