Branko Čibej wrote: > William A. Rowe, Jr. wrote: >> Branko Čibej wrote: >> >>> FYI, I'm waiting for someone to send me the code that I'd made work on >>> Win64. In restrospect, it's quite possible that I only fixed it for the >>> static-link case -- DLLs do have their own ctor/dtor segments, but I'm >>> not sure that they're noticed at program shutdown or library close. >>> >>> I'll know more in a few days. >>> >> >> That sounds great - we'll be patient :) But there is the thought of >> doing a release at the end of the week, so once you do hear word, let us >> know.
You note I've sort of let the new tarballs slip a bit, I don't like the idea of rapid-firing alot more 0.9 releases (hopefully someday soon it will be mostly static.) I've been holding out to look at this issue, and the issue of mac filename case-canonicalization. >> If your solution works only for static-links, and Mladen's works for >> the .dll case, then it seems we could mix n match to solve the whole issue. The more I think about it, the more that the 64bit AMD seems like the exception to solve, not static-links. Let's proceed on this path, and then pick up the 64 bit compilation issues as a second phase. Frankly 0.9 really wasn't 64P ready (while 64LP or 64ILP models compiled fine). So backporting -this- fix to 0.9 and ignoring the 64amd issues doesn't bother me at all for 0.9. For 1.2 / 1.3 it would be nice to solve every case. > Here's the code. This is the tss_pe.cpp file from Boost, slightly > modified (lines 35--37) in order to compile on Win/IA64. It compiles and > runs on x86, AMD64 and IA64, but I only ever tested it as a static > library. It's also C++, and quite possible that the same method won't > work in C. Thanks Branko - and Mladen - I'm studying the code, Mladen's interpretation for threadpriv.c and compilation on vc 6.0, 2002, 2003 and 2005 flavor VS's to determine if this is the best solution, and should be ready to comment more tomorrow. I'm especially interested in the emits Mladen later reported which I'll work on diagnosing and explaining. It might take a bit of reverse engineering.
