[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2024-04-10 Thread meissner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Bug 104772 depends on bug 99708, which changed state. Bug 99708 Summary: __SIZEOF_FLOAT128__ not defined on powerpc64le-linux https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99708 What|Removed |Added -

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-06-06 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-06-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #11 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:6261d10521f9fdc2a43d54b4dc365025288aa8e9 commit r14-1582-g6261d10521f9fdc2a43d54b4dc365025288aa8e9 Author: Jonathan Wakely Date

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-31 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #10 from Jakub Jelinek --- And the reason for the helper functions is C++11 which would not like temporaries in constexpr functions.

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-31 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #9 from Jakub Jelinek --- Sorry, 0x1.0p-1016 * 0x1.0p-1016 * 0x1.0p-1016 obviously should have been 0x1.0p+1016 * 0x1.0p+1016 * 0x1.0p+1016, I tested it on a testcase where I used different names etc.

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-31 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #8 from Jakub Jelinek --- Dunno. I think you can add support even without any compiler changes, at least if _GLIBCXX_DOUBLE_IS_IEEE_BINARY64: #ifdef __STRICT_ANSI__   static _GLIBCXX_CONSTEXPR __float128   min() _GLIBCXX_USE

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-31 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Jonathan Wakely changed: What|Removed |Added Target Milestone|13.2|14.0 --- Comment #7 from Jonathan Wak

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-31 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #6 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:f150a084e25eaa98afaf25e2211001047ecc8d44 commit r14-1433-gf150a084e25eaa98afaf25e2211001047ecc8d44 Author: Jonathan Wakely Date:

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #5 from Jonathan Wakely --- That would be great :-)

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-05-16 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #4

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2023-04-25 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Richard Biener changed: What|Removed |Added Target Milestone|13.0|13.2 --- Comment #3 from Richard Biene

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2022-03-07 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Jonathan Wakely changed: What|Removed |Added Target Milestone|--- |13.0

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2022-03-03 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2022-03-03 Ever confirmed|0

[Bug libstdc++/104772] std::numeric_limits<__float128> should be specialized

2022-03-03 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772 --- Comment #1 from Jonathan Wakely --- Strictly speaking, the __FLT128_* macros relate to _Float128 which is not defined for C++ even when __float128 is (and in theory a target could have a non-IEEE __float128 which would have different propert