This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/12855] Thread safety problems in ios_base::Init
- From: "carlo at alinoe dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Dec 2003 04:38:13 -0000
- Subject: [Bug libstdc++/12855] Thread safety problems in ios_base::Init
- References: <20031031094301.12855.peturr02@ru.is>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From carlo at alinoe dot com 2003-12-17 04:38 -------
Subject: Re: Thread safety problems in ios_base::Init
On Tue, Dec 16, 2003 at 05:53:47PM -0000, bkoz at gcc dot gnu dot org wrote:
> We've moved to zero-alloc initialization: no allocator, no malloc, no new. (Only
> placement new). There should be no allocation in initialization anymore
> (valgrind tells me this at least). This is by design, and is not likely to
> change, ever.
>
> Does this make you feel more at ease?
Ok, then this extension can be removed - because it is redundant, by design.
If I ever run into problems again because of this, then we can always
add it back }:-)... or rather remove the call to malloc that then was
added by accident.
Thanks
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12855