Correct libgcc complex multiply excess precision handling

[Bernd Schmidt]

On 09/07/2016 11:48 PM, Joseph Myers wrote:
> libgcc complex multiply is meant to eliminate excess
> precision from certain internal values by forcing them to memory in
> exactly those cases where the type has excess precision.  But in
> https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01894.html I
> accidentally inverted the logic so that values get forced to memory in
> exactly the cases where it's not needed.  (This is a pessimization in
> the no-excess-precision case, in principle could lead to bad results
> depending on code generation in the excess-precision case.  Note: I do
> not have a test demonstrating bad results.)

Ok.


Bernd