public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
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:26:00 -0000	[thread overview]
Message-ID: <20021206212601.7715.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Kyle Lanclos <lanclos@ucolick.org>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: optimization/7778: Internal compiler error in reload_cse_simplify_operands
Date: Fri, 6 Dec 2002 15:22:14 -0600 (CST)

 > >     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.
 
 The way this goes is: you see which file the compiler barfs at. Go into 
 this directory and do the exact same command line that was used to compile 
 it previously (when you used make). This command line is the last one that 
 is printed, of course. Then just add -save-temps to the command line. The 
 compiler will still die, but it will have generated a .i file. This is the 
 file we need.
 
 Thanks
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 13:26 Wolfgang 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:16 Kyle Lanclos
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=20021206212601.7715.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).