From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-144058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20584 invoked by alias); 24 May 2005 07:24:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 20572 invoked by uid 48); 24 May 2005 07:24:40 -0000
Date: Tue, 24 May 2005 07:47:00 -0000
From: "Ralf_Recker at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20050524072438.21732.Ralf_Recker@gmx.de>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug tree-optimization/21732] New: -ftree-dump-all-details hangs during *.c.t24.copyprop or *.c.t38.copyprop2
X-Bugzilla-Reason: CC
X-SW-Source: 2005-05/txt/msg03249.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

When dumping the trees during compilation GCC-4.1-2005010[1,8] went into
an endless loop during the *.c.t22.copyprop or the *.c.t37.copyprop2 dump, thus
generating larger and larger files. After the file reaches 2GB in size gcc stops.

The same happens with gcc-4.1-20050515 in the steps *.c.t24.copyprop or
*.c.t38.copyprop2.

The dumper seems to follow and print a copy propagation chain like this in all
the cases: A->B->A->B->A->B->...

I've observed this behaviour with many source files.

-- 
           Summary: -ftree-dump-all-details hangs during *.c.t24.copyprop or
                    *.c.t38.copyprop2
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Ralf_Recker at gmx dot de
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21732