[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #25 from Jakub Jelinek

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Richard Biener changed: What|Removed |Added Target Milestone|13.2|13.3 --- Comment #24 from Richard

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Richard Biener changed: What|Removed |Added Target Milestone|13.0|13.2 --- Comment #23 from Richard

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Jonathan Wakely changed: What|Removed |Added Status|SUSPENDED |NEW

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Dvir Yitzchaki changed: What|Removed |Added CC||dvirtz at gmail dot com --- Comment

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #21 from Paul A. Bristow --- I also note that https://en.cppreference.com/w/cpp/io/manip/fixed Notes Hexadecimal floating-point formatting ignores the stream precision specification, as required by the specification of

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #20 from Jonathan Wakely --- I'll ask the new LWG chair to bump the issue.

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #19 from Maxim Egorushkin --- (In reply to Jonathan Wakely from comment #17) > At this time LWG 2381 is still open. Until the proposed fix (or some other > fix) is resolved by making a change to the draft standard, I do not want to

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Paul A. Bristow changed: What|Removed |Added CC||pbristow at hetp dot u-net.com ---

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #17 from Jonathan Wakely --- For the avoidance of doubt: C++98 did not support reading hex floats from an istream. Libstdc++ still follows the C++98 spec, so does not read hex floats. "0x1" is read as "0". "0x1p1" is also read as

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #16 from Jonathan Wakely --- (In reply to Ben Woodard from comment #15) > IMHO you have not yet effectively made the case this is related to 2381. Read comment 14 again. > Your assertions are not at all consistent with the text of

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #15 from Ben Woodard --- (In reply to Jonathan Wakely from comment #11) > (In reply to Ben Woodard from comment #10) > > Also note: > > https://connect.microsoft.com/VisualStudio/feedback/details/742775 > > > > My reading of: > >

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #14 from Jonathan Wakely --- Yes that's expected. It's the same issue. Libstdc++ still follows the C++98 spec which means there is no such thing as a hex float, and so "0x" cannot be the start of a floating point value, it's just

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #13 from Heinz Kohl --- O.k., but following your arguments I'd expect 0xb as result for my second example 0xb.3590da0e2a06736p-3 (attachment 41578), but it's giving 0, also stopping at 'x' and not at '.', just as

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #12 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #11) > (In reply to Ben Woodard from comment #10) > > Also note: > > https://connect.microsoft.com/VisualStudio/feedback/details/742775 > > > > My reading of: >

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #11 from Jonathan Wakely --- (In reply to Ben Woodard from comment #10) > Also note: https://connect.microsoft.com/VisualStudio/feedback/details/742775 > > My reading of: > https://wg21.link/lwg2381 > > is that if the first part of

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #10 from Ben Woodard --- Also note: https://connect.microsoft.com/VisualStudio/feedback/details/742775 My reading of: https://wg21.link/lwg2381 is that if the first part of the number includes a '.' then the portion after the 'p'

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #9 from Jonathan Wakely --- (In reply to Heinz Kohl from comment #8) > o.k., it looks like a flawy definition. Yes, that's why it's being fixed by the standards committee. I don't want to change our implementation yet, until the

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #8 from Heinz Kohl --- o.k., it looks like a flawy definition. First of all, it would be nice, if you would refer my error message to the right instance. It's unclear, what's to do in the meantime. An idea might

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #7 from Jonathan Wakely --- (In reply to Ben Woodard from comment #5) > The example code in: http://en.cppreference.com/w/cpp/io/manip/fixed > suggests that this should work. Probably either the behavior or the library > or the

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #6 from Jonathan Wakely --- (In reply to Ben Woodard from comment #4) > Without this Is there a way to read and write floats and doubles accurately > without the rounding that converting to/from base 10 ends up introducing? > How are

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #5 from Ben Woodard --- The example code in: http://en.cppreference.com/w/cpp/io/manip/fixed suggests that this should work. Probably either the behavior or the library or the example on cppreference should change.

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #4 from Ben Woodard --- Without this Is there a way to read and write floats and doubles accurately without the rounding that converting to/from base 10 ends up introducing? How are you supposed to use istreams like

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 Jonathan Wakely changed: What|Removed |Added Status|NEW |SUSPENDED Summary|parsing