public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dennis Lubert <plasmahh@informatik.uni-bremen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8413: internal compiler error
Date: Thu, 31 Oct 2002 04:16:00 -0000	[thread overview]
Message-ID: <20021031121602.28385.qmail@sources.redhat.com> (raw)

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

From: Dennis Lubert <plasmahh@informatik.uni-bremen.de>
To: paolo@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, plasmahh@tzi.de, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8413: internal compiler error
Date: Thu, 31 Oct 2002 12:11:24 +0000

 On Thu, Oct 31, 2002 at 11:01:59AM -0000, paolo@gcc.gnu.org wrote:
 > Synopsis: internal compiler error
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: paolo
 > State-Changed-When: Thu Oct 31 03:01:57 2002
 > State-Changed-Why:
 >     Please follow the detailed bug reporting instructions
 >     http://gcc.gnu.org/bugs.html#detailed
 >     providing a self contained *.ii preprocessed file.
 >     Thanks, Paolo.
 Well, this is curious. regarding to the g++ manpage, the compiler will stop after preprocessor stage when giving -E option. But it doesn't, it will succesfully compile the file !!! but not without -E option... I can't find a proper way to get the .ii file, sorry. perhaps you can reproduce this error with gcc-3.2 and the kismet sources, where I gave the url....
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8413


             reply	other threads:[~2002-10-31 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  4:16 Dennis Lubert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31  4:35 paolo
2002-10-31  4:26 Paolo Carlini
2002-10-31  3:02 paolo
2002-10-31  2:56 plasmahh

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=20021031121602.28385.qmail@sources.redhat.com \
    --to=plasmahh@informatik.uni-bremen.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: 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).