From: "Joseph S. Myers" <joseph@codesourcery.com>
To: David Miller <davem@davemloft.net>
Cc: joel.sherrill@OARcorp.com, gcc@gcc.gnu.org,
gcc-patches@gcc.gnu.org, ro@CeBiTec.Uni-Bielefeld.DE
Subject: Re: serious libgcc regression added recently
Date: Thu, 03 Nov 2011 03:22:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1111030119080.15392@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20111102.211631.2191289155791292216.davem@davemloft.net>
On Wed, 2 Nov 2011, David Miller wrote:
> > ${host} is the *target* when configuring target libraries.
>
> It doesn't represent the 'target' we're generating code for in
> a multilib instance so we can conditionalize off of it correctly.
>
> The only way sparc/t-softfp can be added to tmake is if the host
> matches sparc-*-* and that's what happens even when we're building
> the 64-bit libgcc in my case.
>
> It's sparc-*-* for both the 32-bit and 64-bit libgcc builds.
Yes, there is nothing new there - when this configuration was in the gcc/
directory the target name was also the same for both builds. What is new
is that you can now put tests in libgcc/configure.ac such as the "Check
32bit or 64bit for x86." one, and select t-* files based on those tests -
whereas in the gcc/ directory there is no possibility at all for the
choice of t-* files to depend on the multilib.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-11-03 1:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 20:49 David Miller
2011-11-02 22:10 ` Joel Sherrill
2011-11-02 22:52 ` David Miller
2011-11-02 23:06 ` David Miller
2011-11-03 0:22 ` David Miller
2011-11-03 0:23 ` Andrew Pinski
2011-11-03 1:25 ` David Miller
2011-11-03 0:35 ` Joseph S. Myers
2011-11-03 0:32 ` Joseph S. Myers
2011-11-03 1:51 ` David Miller
2011-11-03 3:22 ` Joseph S. Myers [this message]
2011-11-03 4:53 ` David Miller
2011-11-03 9:00 ` Paolo Bonzini
2011-11-03 9:16 ` Jakub Jelinek
2011-11-04 7:50 ` David Miller
2011-11-05 3:23 ` David Miller
2011-11-03 14:17 ` Joel Sherrill
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=Pine.LNX.4.64.1111030119080.15392@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=davem@davemloft.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=joel.sherrill@OARcorp.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).