public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Ritzert@t-online.de (Michael Ritzert) To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9304: [pch] ICE in gen_subprogram_die Date: Tue, 04 Feb 2003 18:46:00 -0000 [thread overview] Message-ID: <20030204184600.11932.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 19:38:50 +0100 On February 4th 2003 15:38 schrieb Wolfgang Bangerth: > > I will see what I am doing wrong and report back. > > I guess you do, but can you also say whether this is a recent snapshot, or > from which date it stems? Reading specs from /opt/gcc-HEAD/lib/gcc-lib/i686-pc-linux-gnu/3.4/specs Configured with: /home/ritzert/gcc/HEAD/gcc/configure --enable-threads=posix --prefix=/opt/gcc-HEAD Thread model: posix gcc version 3.4 20030202 (experimental) I looked into it briefly, but I can't find anything obvious I'm doing wrong. - I'm compiling the header and the actual source file with exactly the same flags. - When I don't use pch the error disappears. - When I try to reproduce with preprocessed sources where I replace the content of the header in question with #include <cdefs.h>, I can't reproduce it. So all I can say ATM is that "strange things happen"... I will compile today's CVS over night and test again. Michael
next reply other threads:[~2003-02-04 18:46 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-04 18:46 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:56 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 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=20030204184600.11932.qmail@sources.redhat.com \ --to=ritzert@t-online.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).