[Bug libstdc++/87635] backport of cmath patches to gcc 48 for Darwin incomplete cmath

2018-11-21 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87635

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from Jonathan Wakely  ---
(In reply to Riccardo from comment #2)
> Given your comment, I don't think it is worth opening a new bug just for
> that?

Right, but the patches will be attached here for anybody who needs them.

Closing as WONTFIX then.

[Bug libstdc++/87635] backport of cmath patches to gcc 48 for Darwin incomplete cmath

2018-11-20 Thread rm at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87635

--- Comment #3 from Riccardo  ---
Created attachment 45047
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45047=edit
Same patches for gcc6

Backport of patches but for gcc 6.5

[Bug libstdc++/87635] backport of cmath patches to gcc 48 for Darwin incomplete cmath

2018-11-20 Thread rm at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87635

--- Comment #2 from Riccardo  ---
Just for the reference, I backported the fix also to gcc 6.5
It applied almost cleanly.

Given your comment, I don't think it is worth opening a new bug just for that?
So I leave the patch here for the record.

[Bug libstdc++/87635] backport of cmath patches to gcc 48 for Darwin incomplete cmath

2018-10-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87635

--- Comment #1 from Jonathan Wakely  ---
(In reply to Riccardo from comment #0)
> The support for this is very useful for compiling larger software which
> still needs gcc 48, as is the case of TenFourFox!

GCC 4.8 is no longer supported or maintained, so nothing is going to be
backported to that branch here (downstream vendors might still support it and
make changes to their versions).

> Compared to the referenced bug, the issue is not PPC only, but also x86!

Those fields were set incorrectly, I've changed them now.

> I would also plan backporting to gcc6.

The gcc-6 branch is going to close in the next week or two, so I doubt this
will get backported to that branch either, unless it fixes a regression in GCC
6.4 when compared to previous releases.