public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com> To: nickc@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6172: [fr30-elf] does not build Date: Wed, 11 Dec 2002 16:36:00 -0000 [thread overview] Message-ID: <20021212003601.31619.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6172; it has been noted by GNATS. From: Joel Sherrill <joel.sherrill@OARcorp.com> To: Hans-Peter Nilsson <hp@bitrange.com> Cc: Nick Clifton <nickc@redhat.com>, joel@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/6172: [fr30-elf] does not build Date: Wed, 11 Dec 2002 18:31:46 -0600 Hans-Peter Nilsson wrote: > > On Wed, 11 Dec 2002, Joel Sherrill wrote: > > I think this got it further. Now it dies here: > > ../../../../../gcc-3.2.1/newlib/libc/stdlib/strtod.c:712: Internal > > compiler error in extract_insn, at recog.c:2148 > > > > Do you want me to close this PR and open another or continue? > > It is already closed, because there's no build problem on the > main trunk, evidently due to Nick's patch. (No execute *tests* > seem so succeed unfortunately. :-( ) As I wrote in the closing > comment, please open another PR for 3.2.x. Done. Now that you mention test suite.. has anyone successfully run test_installed on a cross toolset? I would like some hints. :) Thanks. > brgds, H-P -- 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-12-12 0:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-11 16:36 Joel Sherrill [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-11 16:26 Hans-Peter Nilsson 2002-12-11 16:16 Joel Sherrill 2002-12-09 9:56 Hans-Peter Nilsson 2002-12-08 21:12 hp 2002-12-05 10:36 Nick Clifton 2002-12-05 7:23 joel
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=20021212003601.31619.qmail@sources.redhat.com \ --to=joel.sherrill@oarcorp.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nickc@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: linkBe 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).