public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: pb@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/5209: 3.0.3, arm-linux: segfault building libstdc++
Date: Mon, 11 Feb 2002 11:56:00 -0000	[thread overview]
Message-ID: <20020211195602.25027.qmail@sources.redhat.com> (raw)

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

From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: pb@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, philb@gnu.org,
   xkaspa06@stud.fee.vutbr.cz, joel@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/5209: 3.0.3, arm-linux: segfault building libstdc++
Date: Mon, 11 Feb 2002 13:40:14 -0600

 pb@gcc.gnu.org wrote:
 > 
 > Synopsis: 3.0.3, arm-linux: segfault building libstdc++
 > 
 > State-Changed-From-To: analyzed->feedback
 > State-Changed-By: pb
 > State-Changed-When: Mon Feb 11 05:50:28 2002
 > State-Changed-Why:
 >     proposed patch at:
 >     http://gcc.gnu.org/ml/gcc-patches/2002-02/msg00627.html
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5209
 
 This has fixed the problem I was having with arm-elf and 
 arm-rtems on the gcc 3.0-branch.  You can close it.
 
 Thanks.
 
 -- 
 Joel Sherrill, Ph.D.             Director of Research & Development
 joel@OARcorp.com                 On-Line Applications Research
 Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985


             reply	other threads:[~2002-02-11 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 11:56 Joel Sherrill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-13 14:30 pb
2002-02-11  5:50 pb
2002-02-08 15:19 pb
2001-12-28  3:16 philb

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=20020211195602.25027.qmail@sources.redhat.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=pb@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).