From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18137 invoked by alias); 17 Mar 2003 23:26:04 -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 18041 invoked by uid 71); 17 Mar 2003 23:26:01 -0000 Date: Mon, 17 Mar 2003 23:26:00 -0000 Message-ID: <20030317232601.18036.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: bootstrap/10098: gcc internal error: illegal instruction (fwd) Reply-To: Wolfgang Bangerth X-SW-Source: 2003-03/txt/msg01172.txt.bz2 List-Id: The following reply was made to PR bootstrap/10098; it has been noted by GNATS. From: Wolfgang Bangerth To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/10098: gcc internal error: illegal instruction (fwd) Date: Mon, 17 Mar 2003 17:23:38 -0600 (CST) ---------- Forwarded message ---------- Date: Sun, 16 Mar 2003 01:45:17 +0100 From: Giovanni Bajo To: Daniel Frankowski Cc: bangerth@dealii.org Subject: Re: bootstrap/10098: gcc internal error: illegal instruction > Giovanni, > Thanks for your rapid reply! You're welcome. > What did you try to reproduce the problem? Download the .i and > compile the .i file with the given command line? I should try exactly > what you did. > I don't quite know how to proceed. Can I get more detail on exactly > what is failing somehow? Downloaded the .i, and compiled it using simply g++ -c. I tried with both 3.2 (exactly your release) and 3.2.2 (for mingw) and they both work. I simply cannot reproduce your bug. Can you doublecheck that the .i you sent can ICE the compiler simply with "g++ -c filename.i" ? > Unfortunately in the Windows environment, it > is always possible that something unrelated to gcc somehow makes it > unstable. I use both Windows 2000 and XP with no stability problems at all. I agree that stability is fuzzy under 9x. > Any other suggestions? Not really. Maybe you can try downloading latest mingw and compiling the .i with it, to see if it still ICE your compiler. Wolfgang, I assume you cannot reproduce the bug as well on your system? Giovanni Bajo