From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: <binutils@sourceware.org>
Subject: Re: [PATCH] MIPS: Enable NewABI testing for all Linux targets
Date: Tue, 07 Aug 2012 08:25:00 -0000 [thread overview]
Message-ID: <878vdrjhz8.fsf@talisman.home> (raw)
In-Reply-To: <alpine.DEB.1.10.1208062228570.20608@tp.orcam.me.uk> (Maciej W. Rozycki's message of "Mon, 6 Aug 2012 22:39:05 +0100")
"Maciej W. Rozycki" <macro@codesourcery.com> writes:
> On Sat, 4 Aug 2012, Richard Sandiford wrote:
>> > Can you comment on my concerns about config.bfd too?
>>
>> Not including the targets in the BFD64 block at the time that the
>> extra vectors were added was probably an oversight.
>
> I've been wondering if these extra vectors were added by mistake instead,
> like slipped through in a larger commit unnoticed. I'll post a fix to the
> BFD64 block separately.
The 64-bit ones? No, Debian wanted to allow 32-bit *-linux-gnu targets
that provice all three ABIs, while still defaulting to o32. The associated
GCC configure option is --enable-targets=all. (Confusingly different from
the binutils meaning, but there you go. That choice of name wasn't a MIPS
invention.)
>> Providing a separate configuration that isn't BFD64 and doesn't have the
>> extra vectors seems more trouble than it's worth TBH. If you disagree
>> though, please go ahead.
>
> My understanding is it only really matters for hosts that do not have a
> 64-bit integer type and therefore cannot handle 64-bit quantities. In
> which case I couldn't care less, GCC has supported 64-bit long long on
> 32-bit hosts since time immemorial and the last teething problems in this
> area I seem to remember went away in late 1990s.
Indeed. And MIPS GCC requires 64-bit HWIs regardless of whether you're
compiling for a 32-bit or 64-bit target.
Richard
next prev parent reply other threads:[~2012-08-07 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 15:22 Maciej W. Rozycki
2012-08-02 18:48 ` Richard Sandiford
2012-08-02 19:25 ` Maciej W. Rozycki
2012-08-04 18:32 ` Richard Sandiford
2012-08-06 21:45 ` Maciej W. Rozycki
2012-08-07 8:25 ` Richard Sandiford [this message]
2012-08-10 13:19 ` Maciej W. Rozycki
2012-08-12 18:34 ` Richard Sandiford
2012-08-13 15:21 ` Maciej W. Rozycki
2012-08-03 7:38 ` Alan Modra
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=878vdrjhz8.fsf@talisman.home \
--to=rdsandiford@googlemail.com \
--cc=binutils@sourceware.org \
--cc=macro@codesourcery.com \
/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).