public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/21072] base allocator change shared object issues
       [not found] <bug-21072-365@http.gcc.gnu.org/bugzilla/>
@ 2005-11-04 14:45 ` matz at suse dot de
  2005-11-04 17:41 ` bkoz at gcc dot gnu dot org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 9+ messages in thread
From: matz at suse dot de @ 2005-11-04 14:45 UTC (permalink / raw)
  To: gcc-bugs



------- 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?


-- 

matz at suse dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matz at suse dot de


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
       [not found] <bug-21072-365@http.gcc.gnu.org/bugzilla/>
  2005-11-04 14:45 ` [Bug libstdc++/21072] base allocator change shared object issues matz at suse dot de
@ 2005-11-04 17:41 ` bkoz at gcc dot gnu dot org
  2005-11-07 19:59 ` matz at suse dot de
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu dot org @ 2005-11-04 17:41 UTC (permalink / raw)
  To: gcc-bugs



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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
       [not found] <bug-21072-365@http.gcc.gnu.org/bugzilla/>
  2005-11-04 14:45 ` [Bug libstdc++/21072] base allocator change shared object issues matz at suse dot de
  2005-11-04 17:41 ` bkoz at gcc dot gnu dot org
@ 2005-11-07 19:59 ` matz at suse dot de
  2005-11-08 23:12 ` bkoz at gcc dot gnu dot org
  2006-10-08  1:32 ` pcarlini at suse dot de
  4 siblings, 0 replies; 9+ messages in thread
From: matz at suse dot de @ 2005-11-07 19:59 UTC (permalink / raw)
  To: gcc-bugs



------- 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, and
4.0 compiled programs work with the trunk libstc++, which has the same
SOname like the 4.0 one).  I think the only way to switch to the 'mt'
allocator by default for the future without API issues would be to rename
it to 'new', and not via some configure arguments.

Another reason is that this switching back of the default allocator is
not forgotten when 4.1 branches, which I think is necessary anyway, so that
4.1 libs are compatible with 4.0 programs.


-- 


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
       [not found] <bug-21072-365@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2005-11-07 19:59 ` matz at suse dot de
@ 2005-11-08 23:12 ` bkoz at gcc dot gnu dot org
  2006-10-08  1:32 ` pcarlini at suse dot de
  4 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu dot org @ 2005-11-08 23:12 UTC (permalink / raw)
  To: gcc-bugs



------- 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
allocator choices should be standard.


-- 


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
       [not found] <bug-21072-365@http.gcc.gnu.org/bugzilla/>
                   ` (3 preceding siblings ...)
  2005-11-08 23:12 ` bkoz at gcc dot gnu dot org
@ 2006-10-08  1:32 ` pcarlini at suse dot de
  4 siblings, 0 replies; 9+ messages in thread
From: pcarlini at suse dot de @ 2006-10-08  1:32 UTC (permalink / raw)
  To: gcc-bugs



------- 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                 |RESOLVED
         Resolution|                            |FIXED


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
  2005-04-17 17:56 [Bug libstdc++/21072] New: " bkoz at gcc dot gnu dot org
                   ` (2 preceding siblings ...)
  2005-04-17 17:59 ` bkoz at gcc dot gnu dot org
@ 2005-04-17 18:27 ` pcarlini at suse dot de
  3 siblings, 0 replies; 9+ messages in thread
From: pcarlini at suse dot de @ 2005-04-17 18:27 UTC (permalink / raw)
  To: gcc-bugs


------- 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 that we can work around it, 
somehow...

-- 


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
  2005-04-17 17:56 [Bug libstdc++/21072] New: " bkoz at gcc dot gnu dot org
  2005-04-17 17:56 ` [Bug libstdc++/21072] " bkoz at gcc dot gnu dot org
  2005-04-17 17:58 ` bkoz at gcc dot gnu dot org
@ 2005-04-17 17:59 ` bkoz at gcc dot gnu dot org
  2005-04-17 18:27 ` pcarlini at suse dot de
  3 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu dot org @ 2005-04-17 17:59 UTC (permalink / raw)
  To: gcc-bugs


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
  2005-04-17 17:56 [Bug libstdc++/21072] New: " bkoz at gcc dot gnu dot org
  2005-04-17 17:56 ` [Bug libstdc++/21072] " bkoz at gcc dot gnu dot org
@ 2005-04-17 17:58 ` bkoz at gcc dot gnu dot org
  2005-04-17 17:59 ` bkoz at gcc dot gnu dot org
  2005-04-17 18:27 ` pcarlini at suse dot de
  3 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu dot org @ 2005-04-17 17:58 UTC (permalink / raw)
  To: gcc-bugs


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Bug libstdc++/21072] base allocator change shared object issues
  2005-04-17 17:56 [Bug libstdc++/21072] New: " bkoz at gcc dot gnu dot org
@ 2005-04-17 17:56 ` bkoz at gcc dot gnu dot org
  2005-04-17 17:58 ` bkoz at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu dot org @ 2005-04-17 17:56 UTC (permalink / raw)
  To: gcc-bugs


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


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2006-10-08  1:32 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-21072-365@http.gcc.gnu.org/bugzilla/>
2005-11-04 14:45 ` [Bug libstdc++/21072] base allocator change shared object issues matz at suse dot de
2005-11-04 17:41 ` bkoz at gcc dot gnu dot org
2005-11-07 19:59 ` matz at suse dot de
2005-11-08 23:12 ` bkoz at gcc dot gnu dot org
2006-10-08  1:32 ` pcarlini at suse dot de
2005-04-17 17:56 [Bug libstdc++/21072] New: " bkoz at gcc dot gnu dot org
2005-04-17 17:56 ` [Bug libstdc++/21072] " bkoz at gcc dot gnu dot org
2005-04-17 17:58 ` bkoz at gcc dot gnu dot org
2005-04-17 17:59 ` bkoz at gcc dot gnu dot org
2005-04-17 18:27 ` pcarlini at suse dot de

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).