[Bug c++/19351] operator new[] can return heap blocks which are too small

2010-05-23 Thread fw at gcc dot gnu dot org 


--- Comment #21 from fw at gcc dot gnu dot org  2010-05-23 11:04 ---
It turns out that the C++ committee did address this in C++0X, after rejected a
previous DR.  See section 18.6.2.2 in N3090. This seems to require an ABI
change because the size calculation can no longer happen at the call site
without much code bloat.  See
http://gcc.gnu.org/ml/gcc/2010-05/msg00437.html.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351

[Bug c++/19351] operator new[] can return heap blocks which are too small

2010-03-25 Thread fw at gcc dot gnu dot org 


-- 

fw at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|fw at deneb dot enyo dot de |unassigned at gcc dot gnu
   ||dot org
 Status|ASSIGNED|NEW


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351

[Bug c++/19351] operator new[] can return heap blocks which are too small

2010-03-25 Thread fw at gcc dot gnu dot org 


--- Comment #20 from fw at gcc dot gnu dot org  2010-03-25 17:13 ---
(In reply to comment #19)
 You just need a testcase, bootstrap and regression testing.

Test case (and a different patch) is here:

http://gcc.gnu.org/ml/gcc-patches/2010-02/msg00275.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351

[Bug c++/19351] operator new[] can return heap blocks which are too small

2010-02-06 Thread fw at gcc dot gnu dot org 


-- 

fw at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |fw at deneb dot enyo dot de
   |dot org |
 Status|NEW |ASSIGNED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351