public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35659] [4.3/4.4 Regression] Miscompiled code with -O2 (but not with -O2 -funroll-loops) on ia64
Date: Wed, 21 May 2008 10:40:00 -0000 [thread overview]
Message-ID: <20080521103936.31339.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35659-15955@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from rguenth at gcc dot gnu dot org 2008-05-21 10:39 -------
Mark, you made this P5, but ia64-linux is a secondary platform. P3 again to
get it on the radar. But not higher priority because we don't have exactly
what
I would call a testcase.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmitchel at gcc dot gnu dot
| |org
Known to fail| |4.3.0
Priority|P5 |P3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35659
next prev parent reply other threads:[~2008-05-21 10:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 18:49 [Bug fortran/35659] New: " kmccarty at debian dot org
2008-03-22 13:22 ` [Bug target/35659] " rguenth at gcc dot gnu dot org
2008-03-24 16:48 ` kmccarty at debian dot org
2008-03-24 17:33 ` [Bug target/35659] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2008-04-28 4:29 ` mmitchel at gcc dot gnu dot org
2008-05-20 21:02 ` sje at cup dot hp dot com
2008-05-21 3:51 ` kmccarty at debian dot org
2008-05-21 10:40 ` rguenth at gcc dot gnu dot org [this message]
2008-05-23 1:29 ` mmitchel at gcc dot gnu dot org
2008-06-03 18:00 ` sje at cup dot hp dot com
2008-06-04 9:00 ` rguenth at gcc dot gnu dot org
2008-06-06 15:03 ` rguenth at gcc dot gnu dot org
2008-06-24 14:45 ` jakub at gcc dot gnu dot org
2008-06-24 15:05 ` jakub at gcc dot gnu dot org
2008-06-25 10:21 ` jakub at gcc dot gnu dot org
2008-06-25 11:32 ` jakub at gcc dot gnu dot org
2008-06-25 11:33 ` jakub at gcc dot gnu dot org
2008-06-25 21:34 ` mkuvyrkov at gcc dot gnu dot org
2008-06-25 22:16 ` doko at cs dot tu-berlin dot de
2008-06-26 8:02 ` jakub at gcc dot gnu dot org
2008-06-26 8:42 ` jakub at gcc dot gnu dot org
2008-06-26 9:22 ` maxim at codesourcery dot com
2008-06-26 9:24 ` mkuvyrkov at gcc dot gnu dot org
2008-08-01 23:29 ` sje at cup dot hp dot com
2008-08-02 18:16 ` mkuvyrkov at gcc dot gnu dot org
2008-08-04 17:36 ` sje at cup dot hp dot com
2008-08-06 6:26 ` mkuvyrkov at gcc dot gnu dot org
2008-08-06 6:38 ` mkuvyrkov at gcc dot gnu dot org
2008-08-06 6:40 ` mkuvyrkov at gcc dot gnu dot org
2009-02-06 7:33 ` bonzini 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=20080521103936.31339.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).