public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: arbonline@users.sourceforge.net
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/10227: Random segfaults
Date: Wed, 26 Mar 2003 18:16:00 -0000	[thread overview]
Message-ID: <20030326180722.12375.qmail@sources.redhat.com> (raw)


>Number:         10227
>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:


             reply	other threads:[~2003-03-26 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 18:16 arbonline [this message]
2003-03-26 19:36 Steven Bosscher
2003-04-10 14:31 ebotcazou
2003-04-12 18:26 Ian Blanes

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=20030326180722.12375.qmail@sources.redhat.com \
    --to=arbonline@users.sourceforge.net \
    --cc=gcc-gnats@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).