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: Fri, 03 Jan 2003 23:56:00 -0000	[thread overview]
Message-ID: <20030103235601.27013.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: Fri, 3 Jan 2003 17:53:52 -0600 (CST)

 Hi Mack,
 
 > i removed all functions except the one that makes gcc crash. I have also 
 > removed some parts of the code in this function. The file is now ~14000 
 > lines of code, where the function is ~3000 lines and the rest are types, 
 > forward declarations, etc..
 > 
 > If i try to remove any more code in the function the compiler won't crash. 
 > Even if i remove something simple as an assignment the compiler starts to 
 > work. I have also noticed that if i remove an unused type (e.g. typedef 
 > _fpos_t fpos_t;) the compiler starts to work.
 > 
 > Basically i'm stuck, i can't get it smaller than this. Do you have any 
 > "tricks" to reduce the size?
 
 If you can't shorten the testcase further, then so be it. There just seem 
 to be such reports. If you want to try something else, there is a project 
 for automatic reduction of testcases. I haven't tried it myself, and it is 
 said to be slow, but maybe you want something that runs during the night, 
 or on a weekend. Take a look at the Delta Debugging project at
   http://www.st.cs.uni-sb.de/dd/
 
 If you send it to me in private mail, I can attach your somewhat-reduced
 testcase to the PR.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2003-01-03 23:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 23:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 20: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  8:56 Wolfgang Bangerth
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=20030103235601.27013.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).