public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: ghazi@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/10472: [3.4 regression] ICE in instantiate_virtual_regs_lossage
Date: Fri, 02 May 2003 00:36:00 -0000	[thread overview]
Message-ID: <20030502003600.26294.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/10472; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>, <ghazi@gcc.gnu.org>,
   Giovanni Bajo <giovannibajo@libero.it>, <gcc-patches@gcc.gnu.org>
Subject: Re: middle-end/10472: [3.4 regression] ICE in instantiate_virtual_regs_lossage
Date: Thu, 1 May 2003 19:32:14 -0500 (CDT)

 > First I tried to determine under what circumstances and platforms the
 > bug appears.  While the PR was opened against cygwin, it seems it
 > should occur on any x86 target.
 
 I'm sorry, I should have made that clearer: the reduced testcase ICEs on 
 my plain vanilla x86-linux-gnu box with SuSE 8.0.
 
 
 > (and why I'm not being chased with torches and pitchforks)
 
 We write hate-mails these days -- mental torture is just as effective :-)
 
 
 > BTW, IMHO the reduced testcase in the PR is slightly misleading.  It
 > lead me at least to believe the bug had something to do with null
 > pointers.
 
 Again my fault. 
 
 
 > In the mean time, we can disable the optmization on x86 so that cygwin
 > people can resume bootstrap.  (Yes this is lame, sorry I'm not able to
 > provide a proper fix.)
 
 Alternatively, one could work around the bootstrap failure with something 
 like the following instead of your small testcase (I'm surprised this 
 works):
     void foo (char *s)
     {
       char * tmp = __builtin_stpcpy (s, "hi");
       f (tmp);
     }
 That's just as lame, and fragile on top of that, but we don't have to wield 
 the sledgehammer to stomp this bug, it would be simpler to add a testcase 
 and we don't have to remember to re-enable the optimization once someone 
 gets around to fixing the underlying problem. There can't be that many 
 places in gcc where such a fix would be necessary, and Giovanni would 
 surely be willing to find them on his box, right? :-)
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-05-02  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  0:36 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02  0:16 Kaveh R. Ghazi
2003-05-01  4:56 Kaveh R. Ghazi
2003-04-30 21:55 bangerth
2003-04-30 21:46 Janis Johnson
2003-04-29  1:02 bangerth

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=20030502003600.26294.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=ghazi@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).