public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "corsepiu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44793] [4.5/4.6 Regression] libgcc does not include t-ppccomm on rtems
Date: Mon, 05 Jul 2010 04:17:00 -0000 [thread overview]
Message-ID: <20100705041732.29848.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44793-296@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from corsepiu at gcc dot gnu dot org 2010-07-05 04:17 -------
(In reply to comment #6)
> (In reply to comment #5)
> > rtems should be moved to the new style libgcc config and include
> > ./config/rs6000/t-ppccomm .
>
> Hmm. Doesn't RTEMS already do so?
Did you mean libgcc/config.host?
In there, powerpc-*linux is the only target using libgcc/config/rs6000/t-ppccom
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44793
next prev parent reply other threads:[~2010-07-05 4:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 20:13 [Bug target/44793] New: Code generated references undefined symbol joel at gcc dot gnu dot org
2010-07-02 20:14 ` [Bug target/44793] " joel at gcc dot gnu dot org
2010-07-02 20:17 ` [Bug target/44793] New: " Andrew Pinski
2010-07-02 20:17 ` [Bug target/44793] " pinskia at gmail dot com
2010-07-02 20:17 ` joel at gcc dot gnu dot org
2010-07-02 20:31 ` joel at gcc dot gnu dot org
2010-07-05 1:19 ` [Bug target/44793] [4.5/4.6 Regression] libgcc does not include t-ppccomm on rtems pinskia at gcc dot gnu dot org
2010-07-05 3:31 ` corsepiu at gcc dot gnu dot org
2010-07-05 4:17 ` corsepiu at gcc dot gnu dot org [this message]
2010-07-22 8:54 ` rguenth at gcc dot gnu dot org
2010-07-31 9:35 ` rguenth at gcc dot gnu dot org
2010-08-08 20:31 ` joel at gcc dot gnu dot org
[not found] <bug-44793-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 13:25 ` rguenth at gcc dot gnu.org
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=20100705041732.29848.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).