This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ping [PATCH] Fix a deadlock bug in static variable initialization in libsupc++
- From: Paolo Carlini <pcarlini at suse dot de>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: "Doug Kwan (éæå)" <dougkwan at google dot com>, Jason Merrill <jason at redhat dot com>, Eric Botcazou <ebotcazou at libertysurf dot fr>, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Thu, 04 Oct 2007 00:23:51 +0200
- Subject: Re: ping [PATCH] Fix a deadlock bug in static variable initialization in libsupc++
- References: <498552560708021356k5206cebbmc070c183694700e3@mail.gmail.com> <46C37623.1010308@redhat.com> <498552560709171557g2d8b0d76vf1e40483b63612d9@mail.gmail.com> <200709180758.16476.ebotcazou@libertysurf.fr> <46F2C279.1010802@redhat.com> <498552560710031455ka2ce097xe20c08224ff9004@mail.gmail.com> <20071003170832.12822ea4@concorde.artheist.org>
Benjamin Kosnik wrote:
Let's get this in folks.
I agree, 100%. That said, only to better understand the issue, I'd like
to see a minimum of discussion about the binary compatibility issues: is
it guaranteed that it will be possible to link an object build with the
current headers to another built with the new headers and obtain an
overall behavior no worse than the current one? In the remote case that
this is not true, I'm ok anyway with the patch, but that should be clear
to all the interested people and in case a note added to the
documentation about that.
Thanks,
Paolo.