Re[2]: [boost] Windows MSVC thread exit handler for staticly linked Boost.Thread

From: Roland (roland.schwarz_at_[hidden])
Date: 2004-08-05 13:20:32

On Thu, 05 Aug 2004 12:43:11 -0500 "Aaron W. LaFramboise" <aaronrabiddog51_at_[hidden]> wrote:

> I positively cannot account for the behavior you are seeing.  This does
> not happen for me.  Perhaps it was a bug on an earlier version of MSVC6.
>  For reference, CL reports version 12.00.8168 and LINK reports version
> 6.00.8168.

Not wanting to be pedantic, but this is very strange, and perhaps the current situation
still can be improved when we find out the reason for this.

My versions are (got it with --hep switch);
CL: 12.00.8804
LINK: 6.00.8447
which are both from the June Service Pack 6 and both appear to be newer than yours.

> At any rate, I think your suggested implementation is the way to go as
> it gets everything right and works everywhere. :)

I did not yet try your code (thank you btw), but I am afraid, that this will not address the
problem I am seeing entirely since I see 256 bytes between start of .CRT$XLA and
start of .CRT$XLB (where the callback lives).

Yes, and if the compiler does get it right the reordering code simply reduces to a no operation
even when not commented out. However this is only true when AddressOfCallbacks is pointing
to __xl_a. Perhaps I should again use the "real" starting address instead of __xl_a altough
this implies the assuption that _tls_used is really the TLS-dircetory. I tried to avoid this
on behalf of your suggestion.

Roland