From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15658 invoked by alias); 26 Mar 2003 18:16:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 15582 invoked by uid 71); 26 Mar 2003 18:16:01 -0000 Resent-Date: 26 Mar 2003 18:16:01 -0000 Resent-Message-ID: <20030326181601.15581.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, arbonline@users.sourceforge.net Received: (qmail 13556 invoked by uid 48); 26 Mar 2003 18:10:05 -0000 Message-Id: <20030326181005.13555.qmail@sources.redhat.com> Date: Wed, 26 Mar 2003 18:26:00 -0000 From: arbonline@users.sourceforge.net Reply-To: arbonline@users.sourceforge.net To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: bootstrap/10228: Random segfaults X-SW-Source: 2003-03/txt/msg01820.txt.bz2 List-Id: >Number: 10228 >Category: bootstrap >Synopsis: Random segfaults >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Mar 26 18:16:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: arbonline@users.sourceforge.net >Release: gcc-3.2.2 >Organization: >Environment: kernel-2.4.20, glibc-2.3.1, gcc-3.2.1, binutils-2.13, bison-1.875 (all of these compiled with gcc-3.2.1 -march=k6-2 -O2). Amd k6-2, 256MB ram. >Description: Bootstrap fails compiling gcc-3.2.2 or any snapshot after 20021125 (it included, I don't know if any between 20021125 and release fails also). I'm sure gcc-3.2.1 doesn't segfault, I build it 3+ times. I also try to reproduce the segfault on a K7-atlonxp with redhat8 but I can't. Segfault usually happens running xgcc at stage1. Once the bootstrap fail, running make bootstrap again will resume the build without the same segfault (another will happen another one in a few compiles). I know that this info won't help to locate the bug but I post here to know if it happens to somebody else. How I can provide usefull info? >How-To-Repeat: I can't in any other machine. Maybe with gcc-3.2.1 optimized for k6-2 in a k6-2. >Fix: >Release-Note: >Audit-Trail: >Unformatted: