public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30503] ICE using phase 2 bootstrap output cc1 on tree.c
Date: Thu, 18 Jan 2007 18:53:00 -0000	[thread overview]
Message-ID: <20070118185255.4808.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30503-11706@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from malitzke at metronets dot com  2007-01-18 18:52 -------
Prior to patclevel 12900 (about 12880) bootstrap failed even with O1 with
segment error.

For those dismissive folks who either say "It works for me" or claim that it is
the submitters harware fault I can only aver the following:
The work was done on a four processor server with 3G error correcting memory
and    over the last three weeks similar Segmentation errors occured; I have
tried different binutils and different versions of glibc. 

I realize GCC-main is undergoing drastic changes right now. 

day before yesterday cc1 (from phse 1) worked with O1 and bombed out with O2. 
I doubt this cand be reduced to a simple test case as it occurs when trying to 
optimize across procedures. 

Glad to cooperate further. 


-- 


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


  parent reply	other threads:[~2007-01-18 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 18:24 [Bug c/30503] New: " malitzke at metronets dot com
2007-01-18 18:31 ` [Bug c/30503] " malitzke at metronets dot com
2007-01-18 18:38 ` malitzke at metronets dot com
2007-01-18 18:53 ` malitzke at metronets dot com [this message]
2007-01-18 23:40 ` malitzke at metronets dot com
2007-01-18 23:45 ` [Bug middle-end/30503] " pinskia at gcc dot gnu dot org
2007-01-19  0:20 ` malitzke at metronets dot com
2007-01-19  0:24 ` pinskia at gcc dot gnu dot org
2007-01-19  3:55 ` dberlin at gcc dot gnu dot org
2007-01-21  8:59 ` pinskia at gcc dot gnu dot org
2007-04-02 19:39 ` malitzke at metronets dot com
2007-04-02 21:13 ` pinskia at gcc dot gnu dot org

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=20070118185255.4808.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).