public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ritzert@t-online.de (Michael Ritzert)
To: geoffk@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9304: [pch] ICE in gen_subprogram_die
Date: Tue, 04 Feb 2003 23:56:00 -0000	[thread overview]
Message-ID: <20030204235600.12750.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9304; it has been noted by GNATS.

From: Ritzert@t-online.de (Michael Ritzert)
To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/9304: [pch] ICE in gen_subprogram_die
Date: Tue, 4 Feb 2003 22:45:51 +0100

 Ok, some more info:
 
 StdAfx.h: empty(!)
 
 configfile.cpp:
 #include "StdAfx.h"
 #include <iostream>
 
 ============================================================================
 i686-pc-linux-gnu  20030202
 -----------------
 ritzert@liz:~/NFS/test/pch$ c++ -g -O2 -fPIC -c StdAfx.h
 ritzert@liz:~/NFS/test/pch$ c++ -g -O2 -fPIC -c configfile.cpp
 In file included from /opt/gcc-HEAD/include/c++/3.4/iostream:46,
                  from configfile.cpp:2:
 /opt/gcc-HEAD/include/c++/3.4/istream:767: internal compiler error: 
 Segmentation
    fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 ritzert@liz:~/NFS/test/pch$ c++ -g -O2 -fPIC -pthread -c configfile.cpp
 In file included from /opt/gcc-HEAD/include/c++/3.4/iostream:46,
                  from configfile.cpp:3:
 /opt/gcc-HEAD/include/c++/3.4/istream:767: internal compiler error: 
 Segmentation
    fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 ============================================================================
 i386-unknown-freebsd4.7  20030203:
 -----------------------
 -bash-2.05b$ g++    -fPIC   -c StdAfx.h
 -bash-2.05b$ g++    -fPIC   -c configfile.cpp 2>&1 | head
 In file included from /home/ritzert/gcc-HEAD/install/include/c++/3.4/ios:50,
                  from 
 /home/ritzert/gcc-HEAD/install/include/c++/3.4/ostream:45,
                  from 
 /home/ritzert/gcc-HEAD/install/include/c++/3.4/iostream:45,
                  from configfile.cpp:3:
 /home/ritzert/gcc-HEAD/install/include/c++/3.4/streambuf:-23783: internal 
 compiler error: Segmentation
    fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 
 ============================================================================
 alpha-unknown-linux-gnu  20030131 - works
 -----------------------
 
 Michael
 


             reply	other threads:[~2003-02-04 23:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 23:56 Michael Ritzert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23 18:00 geoffk
2003-04-22 17:36 Geoffrey Keating
2003-04-22 17:29 geoffk
2003-02-05 10:16 Michael Ritzert
2003-02-04 23:30 geoffk
2003-02-04 22:54 bangerth
2003-02-04 22:26 Michael Ritzert
2003-02-04 18:56 Michael Ritzert
2003-02-04 18:46 Michael Ritzert
2003-02-04 14:46 Wolfgang Bangerth
2003-02-04 11:06 Michael Ritzert
2003-02-03 18:26 Michael Ritzert
2003-02-01 21:03 bangerth
2003-01-14 11:36 ritzert

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=20030204235600.12750.qmail@sources.redhat.com \
    --to=ritzert@t-online.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=geoffk@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).