From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28654 invoked by alias); 8 Jun 2005 19:55:19 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 28638 invoked by uid 48); 8 Jun 2005 19:55:16 -0000 Date: Wed, 08 Jun 2005 19:55:00 -0000 From: "jsm28 at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org Message-ID: <20050608195515.21967.jsm28@gcc.gnu.org> Reply-To: gcc-bugzilla@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 X-Bugzilla-Reason: CC X-SW-Source: 2005-06/txt/msg01256.txt.bz2 List-Id: 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