[Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator

2007-05-01 Thread gcc at severeweblint dot org
work in pool_allocator Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gcc at severeweblint dot org http://gcc.gnu.org/

[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 iter

[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 su

[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

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

2007-03-26 Thread gcc at severeweblint dot org
check properly. -- Summary: resizing bugs in std::vector Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org Reporte