[Bug libstdc++/31370] resizing bugs in std::vector

2007-04-02 Thread pcarlini at suse dot de
--- Comment #10 from pcarlini at suse dot de 2007-04-02 11:19 --- Fixed for 4.3.0. -- pcarlini at suse dot de changed: What|Removed |Added Status|ASSIGNED

[Bug libstdc++/31370] resizing bugs in std::vector

2007-04-02 Thread paolo at gcc dot gnu dot org
--- Comment #9 from paolo at gcc dot gnu dot org 2007-04-02 11:16 --- Subject: Bug 31370 Author: paolo Date: Mon Apr 2 11:15:50 2007 New Revision: 123424 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123424 Log: 2007-04-02 Matthew Levine <[EMAIL PROTECTED]> Paolo

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-31 Thread pcarlini at suse dot de
--- Comment #8 from pcarlini at suse dot de 2007-03-31 17:52 --- Taking care of it. -- pcarlini at suse dot de changed: What|Removed |Added AssignedTo|unassigned

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-27 Thread pcarlini at suse dot de
--- Comment #7 from pcarlini at suse dot de 2007-03-27 21:03 --- Two quick replies: > 4.2 doesn't fix any of the problems, but it does make the max_size > issue a bit more confusing. Thanks, this is encouraging ;) In any case, nobody said 4.2 fixed any of those problems. However, for s

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-27 Thread gcc at severeweblint dot org
--- Comment #6 from gcc at severeweblint dot org 2007-03-27 20:27 --- 4.2 doesn't fix any of the problems, but it does make the max_size issue a bit more confusing. There is a subtle relationship between vector size and pointers. Pointers can address only SIZE_MAX memory. But iterators

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-27 Thread pcarlini at suse dot de
--- Comment #5 from pcarlini at suse dot de 2007-03-27 09:07 --- Thanks. On the mainline and 4_2-branch we have new definitions of max_size, taking into account, as should be, allocator::max_size. Can you please check the vector bits in this light? (well, about the status of vector, Andr

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-26 Thread fang at csl dot cornell dot edu
--- Comment #4 from fang at csl dot cornell dot edu 2007-03-27 08:52 --- Poor vector, being disrespected as a second-class container once again... :P -- fang at csl dot cornell dot edu changed: What|Removed |Added -

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-26 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-03-27 07:04 --- vector should really go away. It is not really a container at all. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added -

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-26 Thread gcc at severeweblint dot org
--- Comment #2 from gcc at severeweblint dot org 2007-03-27 04:20 --- Created an attachment (id=13293) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13293&action=view) patch This patch fixes all the problems in the cheapest possible way. With it the attached testcase succeedds. It

[Bug libstdc++/31370] resizing bugs in std::vector

2007-03-26 Thread gcc at severeweblint dot org
--- Comment #1 from gcc at severeweblint dot org 2007-03-27 04:08 --- Created an attachment (id=13292) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13292&action=view) testcase This little program pushes some of the boundary cases. It ought to print nothing and exit cleanly. Curre