This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Solving mt_allocator's static initialization ordering problem
- From: Paolo Carlini <pcarlini at suse dot de>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: Brad Spencer <spencer at infointeractive dot com>,libstdc++ at gcc dot gnu dot org, Benjamin Kosnik <bkoz at redhat dot com>
- Date: Wed, 30 Jun 2004 13:48:59 +0200
- Subject: Re: Solving mt_allocator's static initialization ordering problem
- References: <20040506151114.GR21258@eng.infointeractive.com> <20040628173638.GO12291@eng.infointeractive.com> <40E2A433.5050908@suse.de>
Paolo Carlini wrote:
and, more important perhaps, why checking _S_options._M_align at all?
Can't we execute the placement new unconditionally, removing a bit of
fragility?
Oh, now I see, it's because of _S_set_options... I think we can rely on the
linker initializing static storage to zero, however, and therefore your
mechanism seems safe.
Paolo.