On 06/06/14 16:40, Marc Glisse wrote:
On Fri, 6 Jun 2014, Ramana Radhakrishnan wrote:
On Fri, Jun 6, 2014 at 3:16 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
here is a new try on adding __float128 typeinfo to libsupc++. The front-end
part is based on the discussion with Jason yesterday. The libstdc++ part is
copied from:
https://gcc.gnu.org/ml/libstdc++/2014-04/msg00077.html
(which wasn't reviewed), but I changed the testsuite.
Michael will likely need to make some adjustments to his __float128 patch,
but I believe it will only be a small configure tweak.
Ramana, does it look safe for ARM? By the way, do you want to remove the
XFmode defined in arm-modes.def and apparently unused?
Thanks for this though I know Tejas is actually trying to fix AArch64
first and then we'll move on to ARM for cleaning up all these types -
as you realize it's quite a chunky project.
Nice to know. I am a bit afraid it might be hard without breaking ABI
compatibility at least a little. Good luck anyway.
We did talk about that - but our expectation was that these scalar types
are actually not exposed on any interface and are purely for internal
representations.
User land should only be using the vector types from arm_neon.h - in any
case if such types were used in intrinsics land, user-code will not be
portable across compilers anyway.
A patch to remove XFmode is pre-approved.
Even for such a trivial patch, it would be good to do at least a build to
check nothing breaks, but I don't have an easy way to do that (debian
multiarch cross-builds don't work out of the box), it would be better if
one of the people working on ARM could handle it.
Sure, one of us will handle that. Thanks for pointing it out.
Ramana
I'll try and have a look at this patch later today or over the weekend
to see if it doesn't affect ARM / AArch64.
Thanks!
