[Bug libstdc++/21072] base allocator change shared object issues

2006-10-07 Thread pcarlini at suse dot de
--- Comment #9 from pcarlini at suse dot de 2006-10-08 01:32 --- No open issues. -- pcarlini at suse dot de changed: What|Removed |Added Status|UNCONFIRMED

[Bug libstdc++/21072] base allocator change shared object issues

2005-11-08 Thread bkoz at gcc dot gnu dot org
--- Comment #8 from bkoz at gcc dot gnu dot org 2005-11-08 23:12 --- We'd certainly not forget about this on the branch. However, I decided to just go ahead and do this anyway, because it is a change in behavior but mostly because it seems to be confusing people/distros WRT what alloc

[Bug libstdc++/21072] base allocator change shared object issues

2005-11-07 Thread matz at suse dot de
--- Comment #7 from matz at suse dot de 2005-11-07 19:59 --- Of course not. But unaware people trying trunk currently on distros which provided 3.4 or 4.0 will get non-obvious problems, and I'm not sure if that's a good idea (ignoring this problem 4.0 and trunk are nearly compatible, an

[Bug libstdc++/21072] base allocator change shared object issues

2005-11-04 Thread bkoz at gcc dot gnu dot org
--- Comment #6 from bkoz at gcc dot gnu dot org 2005-11-04 17:41 --- In general, we make no claims as to ABI compliance wrt development/trunk versions. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21072

[Bug libstdc++/21072] base allocator change shared object issues

2005-11-04 Thread matz at suse dot de
--- Comment #5 from matz at suse dot de 2005-11-04 14:45 --- While 4.0 had this fixed, trunk still uses the 'mt' allocator by default on linux, and hence is incompatible with 3.4 and 4.0 by default. Is that really intended, or shouldn't also trunk default back to the 'new' allocator?

[Bug libstdc++/21072] base allocator change shared object issues

2005-04-17 Thread pcarlini at suse dot de
--- Additional Comments From pcarlini at suse dot de 2005-04-17 18:27 --- Ick! :( Actually, I clearly remember a message from Mark warning that something could go wrong when using different allocators in different sources, but then forgot about the issue when we switched. I really hope

[Bug libstdc++/21072] base allocator change shared object issues

2005-04-17 Thread bkoz at gcc dot gnu dot org
--- Additional Comments From bkoz at gcc dot gnu dot org 2005-04-17 17:59 --- Additional fixes include adding _M_reclaim_block checks. However, this seems to be patching the symptom, not the disease. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21072

[Bug libstdc++/21072] base allocator change shared object issues

2005-04-17 Thread bkoz at gcc dot gnu dot org
--- Additional Comments From bkoz at gcc dot gnu dot org 2005-04-17 17:57 --- Created an attachment (id=8667) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8667&action=view) revert base allocator change -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21072

[Bug libstdc++/21072] base allocator change shared object issues

2005-04-17 Thread bkoz at gcc dot gnu dot org
--- Additional Comments From bkoz at gcc dot gnu dot org 2005-04-17 17:56 --- Created an attachment (id=8666) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8666&action=view) bug -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21072