public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10098: gcc internal error: illegal instruction (fwd)
Date: Thu, 27 Mar 2003 15:25:00 -0000	[thread overview]
Message-ID: <20030327145600.16509.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/10098: gcc internal error: illegal instruction (fwd)
Date: Thu, 27 Mar 2003 08:53:29 -0600 (CST)

 ---------- Forwarded message ----------
 Date: Wed, 26 Mar 2003 23:40:53 -0600
 From: Daniel Frankowski <dfrankow@winternet.com>
 To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
 Cc: Giovanni Bajo <giovannibajo@libero.it>
 Subject: Re: bootstrap/10098: gcc internal error: illegal instruction
 
 By the way, only a couple of days later, using the Borland C++
 compiler to try to compile the same thing, my computer self-immolated.
 
 I got a new CPU, motherboard, case, etc., and I am having much better
 success compiling now.
 
 Thanks again for your help.
 
 Dan
 
 On Tue, Mar 18, 2003 at 07:32:41AM -0600, Daniel Frankowski wrote:
 > Sadly, closing it seems appropriate.  Thanks for your help.
 > 
 > Dan
 > 
 > On Mon, Mar 17, 2003 at 08:18:11PM -0600, Wolfgang Bangerth wrote:
 > > 
 > > OK, will do. Thanks
 > >   W.
 > > 
 > > As a sidenote: when you send messages like the one below (and the previous 
 > > one I got), you make them look as if _I_ have sent them, which is not 
 > > true. Please change this style of quoting.
 > > 
 > > > ----- Original Message -----
 > > > From: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu>
 > > > To: "Giovanni Bajo" <giovannibajo@libero.it>
 > > > Cc: "Daniel Frankowski" <dfrankow@winternet.com>; <gcc-gnats@gcc.gnu.org>
 > > > Sent: Tuesday, March 18, 2003 12:23 AM
 > > > Subject: Re: bootstrap/10098: gcc internal error: illegal instruction
 > > > 
 > > > Even if it looks very strange to me that unstability of operating system can
 > > > affect compilation this way, I would tend to close this bug, especially if
 > > > it works for everything from 3.2 to mainline. But it's your call.
 > > > 
 > > > Giovanni Bajo
 > > > 
 > > 
 > > -------------------------------------------------------------------------
 > > Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
 > >                               www: http://www.ticam.utexas.edu/~bangerth/
 


             reply	other threads:[~2003-03-27 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 15:25 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-17 23:26 Wolfgang 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=20030327145600.16509.qmail@sources.redhat.com \
    --to=bangerth@ices.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).