On Tue, 2014-07-29 at 10:11 -0700, Mike Stump wrote:
> On Jul 29, 2014, at 7:56 AM, Peter Bergner wrote:
> > Currently, the IBM long double routines in libgcc use a union to construct
> > a long double from two double values. This causes horrific code generation
> > that copies the two double fro
On Wed, 2014-07-30 at 22:13 -0400, David Edelsohn wrote:
> On Tue, Jul 29, 2014 at 10:56 AM, Peter Bergner wrote:
> > libgcc/
> > * config/rs6000/ibm-ldouble.c (typedef union longDblUnion): Delete.
> > (pack_ldouble): New function.
> > (__gcc_qadd): Use it.
> > (__g
On Tue, Jul 29, 2014 at 10:56 AM, Peter Bergner wrote:
> ..after cleaning up the conflicting long double builtins and fixing a
> few bugs in the test cases, I'd like to resubmit the following:
>
> Currently, the IBM long double routines in libgcc use a union to construct
> a long double from two d
On Jul 29, 2014, at 7:56 AM, Peter Bergner wrote:
> Currently, the IBM long double routines in libgcc use a union to construct
> a long double from two double values. This causes horrific code generation
> that copies the two double from the FP registers over to GPRs and back
> again, giving us t
On Mon, 2014-05-05 at 13:33 -0500, Peter Bergner wrote:
> Currently, the IBM long double routines in libgcc use a union to construct
> a long double from two double values. This causes horrific code generation
> that copies the two double from the FP registers over to GPRs and back
> again, giving
