From: "Hale Wang" <hale.wang@arm.com>
To: "'Joseph Myers'" <joseph@codesourcery.com>
Cc: "'GCC Patches'" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] [1/2] [ARM] [libgcc] Support RTABI half-precision conversion functions.
Date: Mon, 13 Apr 2015 08:07:00 -0000 [thread overview]
Message-ID: <001301d075c0$d1ec2870$75c47950$@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1504102024540.6902@digraph.polyomino.org.uk>
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of Joseph Myers
> Sent: Saturday, April 11, 2015 4:30 AM
> To: Hale Wang
> Cc: 'GCC Patches'
> Subject: Re: [PATCH] [1/2] [ARM] [libgcc] Support RTABI half-precision
> conversion functions.
>
> On Fri, 10 Apr 2015, Hale Wang wrote:
>
> > According to the run-time ABI for ARM architecture, this function is
> > allowed to corrupt only the integer core registers permitted to be
> > corrupted by the [AAPCS] (r0-r3, ip, lr, and CPSR). So we can't just
> > simply use the existing GNU conversion functions to implement this
> function.
>
> I don't see that "only". Indeed, at the bottom of page 15 in IHI0043D,
"If the
> FP instruction set is available, implementations of these functions may
use it.
> Consequently, FP hardware-using code that calls one of these helper
> functions directly, or indirectly by calling a function with a
base-standard
> interface, must assume that the FP parameter, result, scratch, and status
> registers might be altered by a call to it.".
Yes, you are right. It's my fault to add the "only" here. Thank you to point
out this.
Beside this, is this patch OK for you?
Hale
>
> (Furthermore, the ideal result on implementations with VFP but not
> hardware half-precision support would be that the software conversions
> interact properly with hardware exceptions and rounding modes (so using
> FPSCR).)
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
next prev parent reply other threads:[~2015-04-13 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 4:27 Hale Wang
2015-04-10 20:29 ` Joseph Myers
2015-04-13 8:07 ` Hale Wang [this message]
2015-04-13 11:25 ` Joseph Myers
2015-04-22 7:50 ` Ramana Radhakrishnan
2015-04-22 8:32 ` Hale Wang
2015-04-22 8:59 ` Ramana Radhakrishnan
2015-04-27 10:33 ` Hale Wang
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='001301d075c0$d1ec2870$75c47950$@arm.com' \
--to=hale.wang@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@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).