public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/37960] FAIL: gcc.dg/pr11492.c (test for bogus messages, line 8) Date: Thu, 30 Oct 2008 20:19:00 -0000 [thread overview] Message-ID: <20081030201702.6477.qmail@sourceware.org> (raw) In-Reply-To: <bug-37960-6095@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from manu at gcc dot gnu dot org 2008-10-30 20:17 ------- (In reply to comment #3) > > I don't know if it is in the Compile Farm, or not. But I can test for you. > I need a way to debug this. I have no idea what the issue is. > Note that AVR has 8-bit chars, 16-bit ints and pointers, 32-bit longs. That doesn't ring a bell. Anyway, this is not a regression. My patch added the testcase. The bogus warning was there already. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.4 Regression] FAIL: |FAIL: gcc.dg/pr11492.c |gcc.dg/pr11492.c (test for |(test for bogus messages, |bogus messages, line 8) |line 8) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37960
next prev parent reply other threads:[~2008-10-30 20:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-30 18:57 [Bug testsuite/37960] New: [4.4 Regression] " eric dot weddington at atmel dot com 2008-10-30 18:58 ` [Bug testsuite/37960] " eric dot weddington at atmel dot com 2008-10-30 19:07 ` manu at gcc dot gnu dot org 2008-10-30 20:00 ` eric dot weddington at atmel dot com 2008-10-30 20:19 ` manu at gcc dot gnu dot org [this message] 2008-10-30 20:29 ` [Bug testsuite/37960] " manu at gcc dot gnu dot org 2008-10-30 20:44 ` eric dot weddington at atmel dot com 2008-10-30 21:19 ` manu at gcc dot gnu dot org 2008-10-31 4:28 ` eric dot weddington at atmel dot com 2009-02-07 15:40 ` manu at gcc dot gnu dot org 2009-03-16 20:01 ` janis at gcc dot gnu dot org 2009-05-01 14:37 ` manu 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=20081030201702.6477.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: linkBe 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).