public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	sameermanagoli@yahoo.com, smanagoli@projects.sdsu.edu
Subject: Re: c++/9983: Internal compiler error
Date: Tue, 11 Mar 2003 22:00:00 -0000	[thread overview]
Message-ID: <20030311220016.10815.qmail@sources.redhat.com> (raw)

Synopsis: Internal compiler error

State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Tue Mar 11 22:00:16 2003
State-Changed-Why:
    Reproduced with 3.2, but already fixed with 3.2.2.
    
    Sameer, for next time you file a bug report: if you get
    an internal compiler error and it tells you a www address,
    and later on I send you the same address twice more, it 
    would be helpful if you could take a look at it. It reads
    that what we need are the _preprocessed_ source, and also 
    that you can generate these with the -save-temps flags.
    We don't want to have one file (as in the first report),
    two files (what you sent me the second time), and we don't
    want to have whole tar archives (as what I got the third
    time). I was lucky that I could reproduce your problem
    from these, but you could have saves us all some time if
    you would have followed the instructions on that page.
    
    Thanks anyway
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9983


             reply	other threads:[~2003-03-11 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 22:00 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-14 20:06 Wolfgang Bangerth
2003-03-14 20:06 smanagoli
2003-03-06 22:23 bangerth

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=20030311220016.10815.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=sameermanagoli@yahoo.com \
    --cc=smanagoli@projects.sdsu.edu \
    /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).