https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
--- Comment #7 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:1d9263f292c3efc4e37c3a88117388e86d19b954
commit r14-4799-g1d9263f292c3efc4e37c3a88117388e86d19b954
Author: Marek Polacek
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
Marek Polacek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
--- Comment #4 from Jakub Jelinek ---
Yeah, that is what I meant. Note, I do see the from_chars inlines even with
-std=c++23
in preprocessed dump when including , the difference is in
#if __cplusplus > 202302L
# include
#endif
in bits/basic_st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
--- Comment #3 from Marek Polacek ---
Did you mean like the following? I have no idea if that's correct but is
suppresses the warnings I see.
In C++23 I don't see the code in the .ii file at all, so it doesn't warn.
--- a/libstdc++-v3/include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
--- Comment #2 from Jakub Jelinek ---
Why doesn't it fail with -std=c++23 though? Was there some C++26 change I'm
not aware of?
In the to_chars cases, we already use float(__value) casts in the
_Float16/__bfloat16_t cases (but others too), so I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111883
--- Comment #1 from Jonathan Wakely ---
I think Jakub wrote that code, but it looks like we just want the explicit
casts. I can add those.
