Segher Boessenkool writes:
> You can write
> double convert (__ibm128 x) { return x; }
> double convert (__ieee128 x) { return x; }
> as well. "__ieee128" and "long double" are the same type then (and the
> same as _Float128 and __float128 as well).
Oh! I see. Thanks!
Going back
Michael Meissner via Gcc writes:
> Because long double mangles the same as either __float128 or __ibm128, you
> cannot write programs like:
>
> double convert (__ibm128x) { return x; }
> double convert (__float128 x) { return x; }
> double convert (long double x) { return x
Segher Boessenkool writes:
> That is a usability problem. Can it be fixed, or will that create its
> own compatibility problems? In practice I mean. If it is, the C
> libraries could fix it up, for new programs, and then after a while the
> kernel can do the sane thing?
>
> How big is the prob
Nicholas Piggin writes:
> +PPC_FEATURE_ARCH_2_05
> +The processor supports the v2.05 userlevel architecture. Processors
> +supporting later architectures also set this feature.
I don't think this bit is enabled when processors support later architectures.
In my tests, this behavior start
Steve Ellcey writes:
> I have a question about building a toolchain that uses (at run time) a
> dynamic linker and system libraries and headers that are in a non-standard
> place.
>
> I just noticed the IBM --with-advance-toolchain option and I would
> like to replicate it for aarch64.
>
> Let me
