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, lanclos@cats.ucsc.edu,
	nobody@gcc.gnu.org
Subject: Re: optimization/7778: Internal compiler error in reload_cse_simplify_operands
Date: Fri, 06 Dec 2002 12:55:00 -0000	[thread overview]
Message-ID: <20021206205547.21014.qmail@sources.redhat.com> (raw)

Synopsis: Internal compiler error in reload_cse_simplify_operands

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Fri Dec  6 12:55:45 2002
State-Changed-Why:
    Please accepts our apologies that nobody has looked into this
    report until now. Do you still have the sources and can
    reproduce the error? We would need the preprocessed source
    file, as described in the bug reporting instructions which
    you can find from the gcc homepage http://gcc.gnu.org.
    
    By the way, are you absolutely sure that you are using
    gcc3.2 for your compilation (check with gcc -v)? The
    output upon the internal error does not mention the 
    gcc web page, which it should with 3.2...
    
    Regards
      Wolfgang

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


             reply	other threads:[~2002-12-06 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 12:55 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-06 13:46 Kyle Lanclos
2002-12-06 13:39 bangerth
2002-12-06 13:26 Wolfgang Bangerth
2002-12-06 13:16 Kyle Lanclos
2002-08-30 10:16 lanclos

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=20021206205547.21014.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=lanclos@cats.ucsc.edu \
    --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).