This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Optimise the fpclassify builtin to perform integer operations when possible
- From: Tamar Christina <tamar dot christina at arm dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, "jakub at redhat dot com" <jakub at redhat dot com>, "rguenther at suse dot de" <rguenther at suse dot de>, "law at redhat dot com" <law at redhat dot com>, nd <nd at arm dot com>
- Date: Tue, 13 Sep 2016 13:29:35 +0100
- Subject: Re: [PATCH] Optimise the fpclassify builtin to perform integer operations when possible
- Authentication-results: sourceware.org; auth=none
- Nodisclaimer: True
- References: <VI1PR0801MB2031BC0C70CCAD966A9B2933FFFF0@VI1PR0801MB2031.eurprd08.prod.outlook.com> <alpine.DEB.2.20.1609122239220.25218@digraph.polyomino.org.uk>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 12/09/16 23:41, Joseph Myers wrote:
Are you making endianness assumptions - specifically, does the
reinterpretation as an integer require that WORDS_BIG_ENDIAN and
FLOAT_WORDS_BIG_ENDIAN are the same? If so, I think that's OK (in that
the only target where they aren't the same seems to be pdp11 which doesn't
use IEEE formats), but probably the code should check explicitly.
No, if I understood the question correctly then this should be ok,
since I always access the float as an integer of equivalent precision.
So a 64bit float will be addressed as a 64bit int.
Tamar