https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87614
--- Comment #5 from Jonathan Wakely ---
We have a concept of "inlining locations" in the compiler, and we only consider
a warning location to be in a system header if all call sites along the
inlining stack are in system headers. It seems that co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87614
Jonathan Wakely changed:
What|Removed |Added
CC||redboltz at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87614
--- Comment #3 from Jonathan Wakely ---
Yes, that warning seems useful. The user has caused a conversion that alters
the value. The fact it happens deep inside libstdc++ headers is only because
the library templates preserve the types all the way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87614
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87614
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
