https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
François Dumont changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
--- Comment #6 from Jonathan Wakely ---
François, I think you fixed this for GCC 7.1, so should we close the bug
report?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
--- Comment #5 from François Dumont ---
Author: fdumont
Date: Mon Jun 20 20:04:25 2016
New Revision: 237617
URL: https://gcc.gnu.org/viewcvs?rev=237617&root=gcc&view=rev
Log:
2016-06-20 François Dumont
PR libstdc++/71181
* in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
--- Comment #4 from François Dumont ---
I guess you are talking about 61667.
I think this report is quite new. At the moment reserve is implemented as
proposed by the Standard but I agree with Alexey that demonstrated behavior is
counterintuitiv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
Jonathan Wakely changed:
What|Removed |Added
CC||fdumont at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
Alexey Dmitriev changed:
What|Removed |Added
Version|5.1.0 |6.1.0
--- Comment #2 from Alexey Dmitr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
--- Comment #1 from Alexey Dmitriev ---
in n4582 it's already not valid as they've change 23.2.5p15 to <=
