public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/21967] New: [4.1 Regression] gcc.dg/tree-ssa/loop-2.c and gcc.dg/tree-ssa/loop-4.c fail
Date: Wed, 08 Jun 2005 19:55:00 -0000 [thread overview]
Message-ID: <20050608195515.21967.jsm28@gcc.gnu.org> (raw)
FAIL: gcc.dg/tree-ssa/loop-2.c scan-tree-dump-times iter 0
has appeared on mainline on 20050608 on at least i686-pc-linux-gnu, hppa64-hpux
and ia64-hpux (boht -milp32 and -mlp64).
FAIL: gcc.dg/tree-ssa/loop-4.c scan-tree-dump-times iter 0
has appeared on mainline on 20050608 on at least i686-pc-linux-gnu and ia64-hpux
(-milp32 only, though it was already failing on hppa64-hpux and -mlp64 ia64-hpux
- bug 20605 - so it just isn't a new failure on those platforms).
As the testcases changed in the relevant day it seems likely to be a testsuite
problem, but it could also be a latent bug which was exposed between when the
patch changing the testcases was tested and when it was applied.
--
Summary: [4.1 Regression] gcc.dg/tree-ssa/loop-2.c and
gcc.dg/tree-ssa/loop-4.c fail
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21967
next reply other threads:[~2005-06-08 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 19:55 jsm28 at gcc dot gnu dot org [this message]
2005-06-08 20:07 ` [Bug testsuite/21967] " pinskia at gcc dot gnu dot org
2005-06-18 15:35 ` hp at gcc dot gnu dot org
2005-06-30 11:07 ` cvs-commit at gcc dot gnu dot org
2005-06-30 12:18 ` pinskia 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=20050608195515.21967.jsm28@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).