This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH], Add IEEE 128-bit floating point to PowerPC, patch #1
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Michael Meissner <meissner at linux dot vnet dot ibm dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>, <dje dot gcc at gmail dot com>
- Date: Tue, 2 Jun 2015 17:55:10 +0000
- Subject: Re: [PATCH], Add IEEE 128-bit floating point to PowerPC, patch #1
- Authentication-results: sourceware.org; auth=none
- References: <20150522212414 dot GA25650 at ibm-tiger dot the-meissners dot org>
Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over
floating-point modes including these modes when they shouldn't, as
discussed previously?
If so, how do you deal (in subsequent patches?) with iterations that
*should* include these modes? In particular, where libgcc uses
__LIBGCC_<mode>_* macros predefined with -fbuilding-libgcc in an
interation in c-cppbuiltin.c, how do you handle getting the relevant
information in libgcc to build applicable libgcc functions for these
modes? (I'm presuming that you do want complex arithmetic to work for
both 128-bit types, for example, although you won't want them to be used
for intermediate conversions in libgcc operations on other types.)
--
Joseph S. Myers
joseph@codesourcery.com