From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-204028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 3220 invoked by alias); 2 Dec 2006 17:57:44 -0000
Received: (qmail 3137 invoked by uid 48); 2 Dec 2006 17:57:30 -0000
Date: Sat, 02 Dec 2006 17:57:00 -0000
Subject: [Bug target/30052]  New: memory hog.
X-Bugzilla-Reason: CC
Message-ID: <bug-30052-7667@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
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
X-SW-Source: 2006-12/txt/msg00213.txt.bz2

attached testcase eats a 1GB of ram, swap and it's killed by OOM.
it works fine on 4.1.2/{all} and 4.2.0/{i386,ppc}.
so, it looks like a 4.2/x86-64 target regression.


-- 
           Summary: memory hog.
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pluto at agmk dot net
GCC target triplet: x86_64-linux


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