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: c/8962: "-O2 -mmmx" makes gcc seg fault
Date: Sat, 21 Dec 2002 08:56:00 -0000	[thread overview]
Message-ID: <20021221165601.3353.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Mack Lobell <macklobell@hotmail.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/8962: "-O2 -mmmx" makes gcc seg fault
Date: Sat, 21 Dec 2002 10:55:13 -0600 (CST)

 > did the following:
 
 Thanks for your experiments. I think there is no need for you to try an 
 even newer snapshot. The only thing you could do is try to strip down the 
 testcase as much as possible, presently it is rather long. We usually do 
 that by first stripping off the line number lines using
   perl -pi -e 's/^#.*\n//g;' expr.i
 so that the compiler gives the _actual_ line number in this file when it 
 crashes. Then try to delete as much stuff from the file as you can. 
 Usually, one can get it down to 20-30 lines and still see the crash. But 
 be warned that this can be a tediuous process that could take 30 minutes 
 to an hour, if you're not frequently doing such things.
 
 Thanks for your help
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21  8:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 20:56 Wolfgang Bangerth
2003-01-03 23:56 Wolfgang Bangerth
2002-12-22  0:56 Mack Lobell
2002-12-21 10:16 Wolfgang Bangerth
2002-12-21  9:46 Mack Lobell
2002-12-21  7:56 Mack Lobell
2002-12-20 20:32 bangerth
2002-12-16  7:16 macklobell

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=20021221165601.3353.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).