public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/49498] [4.7 Regression]: gcc.dg/uninit-pred-8_b.c bogus warning line 20
Date: Tue, 05 Jul 2011 16:05:00 -0000 [thread overview]
Message-ID: <bug-49498-4-JcjkcfYzhU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49498-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49498
--- Comment #5 from Jeffrey A. Law <law at redhat dot com> 2011-07-05 16:05:21 UTC ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/30/11 14:37, xinliangli at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49498
>
> --- Comment #4 from davidxl <xinliangli at gmail dot com> 2011-06-30 20:37:36 UTC ---
> I can to reproduce the problem on x86-64 linux. Can you help provide the
> following dump:
You need to configure for cris-elf.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOEzYmAAoJEBRtltQi2kC74P4H/RrrlfNZtk/e0W26Nr1U4K2G
xZM5Y513BPakr2DyRe4OOtpMquIbRxdOe0aJw0iuUfkDXTEKNaT1h/cePYAJGjYe
Wh8GJhHj7D+WC9OiobOoBiYUmCcF7vIclW0OdcNwPrIfQ328E6zFAr8wJeWvvbGb
gBvB0cu5jMYb7Ls+x7ox7PjdTfqHbrIFZCkMVpKBPe2OYuVtKcyoBErJD7QH1cWs
VeL+bk498CRSQNSHL3j9pr/sTKFp18+I+rrBh/+aKi0FnMfoRYgCpN3/AldQw8Ds
qtzTOCPdR7X5v1Wc19bxlPJvFmes5MQSjEvzMooDmA09JeiW963DA4n08w9NeLg=
=HmIU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-07-05 16:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 0:03 [Bug regression/49498] New: " hp at gcc dot gnu.org
2011-06-22 3:08 ` [Bug regression/49498] " hp at gcc dot gnu.org
2011-06-22 9:16 ` rguenth at gcc dot gnu.org
2011-06-22 17:28 ` law at redhat dot com
2011-06-30 19:43 ` law at redhat dot com
2011-06-30 20:38 ` xinliangli at gmail dot com
2011-07-05 16:05 ` law at redhat dot com [this message]
2011-07-05 16:07 ` law at redhat dot com
2011-07-05 22:53 ` xinliangli at gmail dot com
2011-07-07 16:23 ` law at redhat dot com
2011-07-07 19:32 ` xinliangli at gmail dot com
2011-07-07 21:27 ` law at redhat dot com
2011-07-07 21:52 ` hp at gcc dot gnu.org
2011-07-11 15:29 ` law at redhat dot com
2011-10-15 17:11 ` ktietz at gcc dot gnu.org
2012-03-22 8:49 ` [Bug tree-optimization/49498] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-06-14 8:25 ` rguenth at gcc dot gnu.org
2012-09-20 10:28 ` jakub at gcc dot gnu.org
2012-11-20 7:09 ` amker.cheng at gmail dot com
2012-11-21 13:08 ` pinskia at gcc dot gnu.org
2012-11-21 13:24 ` amker.cheng at gmail dot com
2013-04-11 7:59 ` [Bug tree-optimization/49498] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-06-12 13:47 ` [Bug tree-optimization/49498] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:32 ` [Bug tree-optimization/49498] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:24 ` [Bug tree-optimization/49498] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:00 ` [Bug tree-optimization/49498] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub 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-49498-4-JcjkcfYzhU@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).