public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: Paul Koning <Paul_Koning@dell.com>,
	Ralf Baechle <ralf@linux-mips.org>,
		ANDY KENNEDY <ANDY.KENNEDY@adtran.com>,
	binutils <binutils@sourceware.org>
Subject: Re: ABI, I don't get it...
Date: Thu, 25 Aug 2016 00:01:00 -0000	[thread overview]
Message-ID: <CA+=Sn1mChzzhE77Qz5c87Huds6FK3WQeqc7yhxpX=193QuBE4g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1608241630360.4471@tp.orcam.me.uk>

On Wed, Aug 24, 2016 at 8:46 AM, Maciej W. Rozycki <macro@imgtec.com> wrote:
> On Sun, 14 Aug 2016, Paul_Koning@Dell.com wrote:
>
>> > with a toolchain that was supposedly 64-bit native, hard-float.  Why
>> > the floating point selection is soft, I cannot say.
>>
>> Perhaps because some other MIPS64 machines don't have float?  The
>> Sibyte series comes to mind.  We use soft-float for that reason, even
>> though XLR and XLP do have it.

Also FYI. Octeon 1/+ and Octeon 2 do not have a FPU while Octeon 3
does have one.
Maybe most people now days are targeting the Octeon family :).

Thanks,
Andrew Pinski


>
>  FYI, the SiByte/Broadcom SB-1 processor cores do have an FPU albeit IIRC
> early (A0?) steppings had fatal errata making the unit less than usable
> (they also had other issues making them usable even less).  This may have
> been the reason you have chosen a software configuration which avoids the
> use of the FPU with these processors.  Later revisions were fine.  I've
> used the FPU with a B2 stepping SB-1 myself with no issues; there was a
> later C0 revision as well.
>
>  Ralf (cc-ed) may remember a bit more about the story here.
>
>  FWIW,
>
>   Maciej

  parent reply	other threads:[~2016-08-25  0:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12 22:47 ANDY KENNEDY
2016-08-14 16:03 ` Paul_Koning
2016-08-24 15:46   ` Maciej W. Rozycki
2016-08-24 15:53     ` Paul_Koning
2016-08-24 22:55     ` ANDY KENNEDY
2016-08-24 23:08       ` Maciej W. Rozycki
2016-08-25  0:01     ` Andrew Pinski [this message]
2016-08-15 18:51 ` Maciej W. Rozycki
2016-08-24 15:21   ` Matthew Fortune
2016-08-24 22:52     ` ANDY KENNEDY
2016-08-24 22:59       ` Maciej W. Rozycki
2016-08-24 22:53     ` Maciej W. Rozycki

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='CA+=Sn1mChzzhE77Qz5c87Huds6FK3WQeqc7yhxpX=193QuBE4g@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=ANDY.KENNEDY@adtran.com \
    --cc=Paul_Koning@dell.com \
    --cc=binutils@sourceware.org \
    --cc=macro@imgtec.com \
    --cc=ralf@linux-mips.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).