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: bootstrap/6680: [alphaev5-dec-osf5.0] gcc-3.1 build fails with internal error
Date: Fri, 06 Dec 2002 07:26:00 -0000	[thread overview]
Message-ID: <20021206152621.30698.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/6680: [alphaev5-dec-osf5.0] gcc-3.1 build fails with
 internal error
Date: Fri, 6 Dec 2002 09:16:08 -0600 (CST)

 This valuable piece of information may get things going on osf50.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 
 ---------- Forwarded message ----------
 Date: Fri, 6 Dec 2002 10:27:12 +0100
 From: Emmanuel Thomé <thome@lix.polytechnique.fr>
 To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
 Subject: Re: ICE/bootstrap alpha*-dec-osf5.0
 
 
 The build process completes with -fno-reorder-blocks passed as
 BOOT_CFLAGS ; Rainer Sabelka found this, he is currently ttrying to
 investigate things further.
 
 E.
 


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  7:26 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-21  9:41 ehrhardt
2003-05-21  8:33 Dara Hazeghi
2002-12-05 13:46 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=20021206152621.30698.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).