https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:945e86ddaa6cc7251d7bb57be8bb65f182cd3a0c
commit r13-4167-g945e86ddaa6cc7251d7bb57be8bb65f182cd3a0c
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:0e2c5510e001e5ccbde9e4b7df757e2bba2fdb00
commit r13-4096-g0e2c5510e001e5ccbde9e4b7df757e2bba2fdb00
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
--- Comment #4 from Jonathan Wakely ---
Yes, that looks right.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
--- Comment #2 from Jonathan Wakely ---
Although if the _GLIBCXX_FLOAT_IS_IEEE_BINARY32 macro is not defined, it will
still be ambiguous, because we won't define these overloads:
#if _GLIBCXX_USE_C99_COMPLEX
#if defined(__STDCPP_FLOAT16_T__) &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2022-11-11
Status|UNCONFI
