public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3591: [mcore-elf] GCC 3.0-CVS configuration problem
Date: Wed, 27 Nov 2002 02:16:00 -0000 [thread overview]
Message-ID: <20021119204603.10693.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/3591; it has been noted by GNATS.
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, joel@gcc.gnu.org, nobody@gcc.gnu.org,
gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: bootstrap/3591: [mcore-elf] GCC 3.0-CVS configuration problem
Date: Tue, 19 Nov 2002 14:42:35 -0600
bangerth@dealii.org wrote:
>
> Old Synopsis: GCC 3.0-CVS configuration problem on mcore-elf
> New Synopsis: [mcore-elf] GCC 3.0-CVS configuration problem
Close this. My April 2002 log shows tha tit did indeed find
an exception model.
> State-Changed-From-To: open->feedback
> State-Changed-By: bangerth
> State-Changed-When: Tue Nov 19 12:32:56 2002
> State-Changed-Why:
> This is a rather old bootstrap failure. Can you please
> check whether this still happens with newer versions of gcc
> and report your findings?
>
> The audit trail lists patches for this report, so maybe the
> problem is fixed in the meantime.
> Thanks
> Wolfgang
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3591
--
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
next reply other threads:[~2002-11-19 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 2:16 Joel Sherrill [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 23:36 Joel Sherrill
2002-11-26 19:29 bangerth
2002-11-26 17:45 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=20021119204603.10693.qmail@sources.redhat.com \
--to=joel.sherrill@oarcorp.com \
--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).