public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Kyle Lanclos <lanclos@ucolick.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7778: Internal compiler error in reload_cse_simplify_operands
Date: Fri, 06 Dec 2002 13:16:00 -0000	[thread overview]
Message-ID: <20021206211601.31156.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/7778; it has been noted by GNATS.

From: Kyle Lanclos <lanclos@ucolick.org>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/7778: Internal compiler error in reload_cse_simplify_operands
Date: Fri, 6 Dec 2002 13:10:19 -0800

 You wrote:
 >     Do you still have the sources and can reproduce the error?
 >     We would need the preprocessed source file...
 
 There's no way I can pick out from the mozilla source code which file(s)
 are necessary to reproduce the bug. As much as I hate the presentation,
 all I have is a tarball of my build tree.
 
 http://www.ucolick.org/~lanclos/gcc/
 
 I apologize sincerely at my lack of a concise method of reproducing the
 error.
 
 >     By the way, are you absolutely sure that you are using
 >     gcc3.2 for your compilation (check with gcc -v)?
 
 Yes, though I'm not using gcc 3.2.1, and I have not tried building the
 most recent mozilla source code.
 
 >     The output upon the internal error does not mention the 
 >     gcc web page, which it should with 3.2...
 
 I may have omitted that portion of the error message in my report.
 
 --Kyle


             reply	other threads:[~2002-12-06 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 13:16 Kyle Lanclos [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 12:55 bangerth
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=20021206211601.31156.qmail@sources.redhat.com \
    --to=lanclos@ucolick.org \
    --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).