>> Quick question on 1.0.2 and Visual Studio win64 builds ... is ml64 >> supported or just nasm?
>Quick answer: quantum mechanics. Longer answer: state is unknown till >it's measured. Long answer: reports are not rejected, but >when-in-doubt-use-nasm principle applies, and reaction to reports can as >well be avoiding problem. Well then I will definitely send in my more complete analysis/proposed fixes. >As for supporting MASM in more general terms. You have to do better than >"it's *nice* to have MASM". You have to show why is it so, what is it >MASM offers that NASM doesn't. Even if there are some/any, they would be >weighed against advantages NASM has to offer (such as unconditional >availability for immediate download, possibility to affect the >functionality, cross-platform support). And even then faking nasm is >hardly appropriate way to solve the problem. OpenSSL is security software. I have clients who have auditors that make demands sometimes. I just helped a client get on 1.0.1f because of an issue with 1.0.1e that a government auditor noted. What if the auditors say "and why is it that it cannot be built for the Microsoft platform with the Microsoft platform tools?". It would be SO nice to not have to have that conversation, ever. And if my analysis is correct, OpenSSL is way over 99% of the way there, all the hooks are still there, it is just a little tiny bit of tweaking. I feel like we'd be making a mistake to let this opportunity slip away, now that the native tool MASM is installed even on the free "Express Edition" of Visual Studio 2012/2013 in both 32 and 64 bit. No extra download. Platform vendor tool. Supportable by vendor. Free. Automatic software update mechanism. And faking nasm, well, it is a nasm emulator ... but as the name denotes, I really didn't want to call it a "real" tool exactly. Just one for development analysis work if we can get OpenSSL to use ml/ml64 natively. But if not, I can build it anytime I want to and have control over new features :-) >>> While I am able to build those versions and they pass the "ms\test", I >>> do not have a CPU with Intel® AVX, Intel® AVX2, Intel® AVX-512 ... >>> anybody want to test it on those processors? :-) > http://software.intel.com/en-us/articles/intel-software-development-emulator/ Yes, I tried that, testing / dev tools like this are the inspiration for the fake nasm. Sort of a "just inject this tool in the middle and you can learn some things" so to speak. On the SDE, I was seeing the AVX/AVX2 from my lil CPUID program (not the greatest and the Intel one doesn't seem to work with the Intel SDE!) AVX512 support didn't seem to be turned on in the emulator, I tried the edition released yesterday and the previous one as well. I tried the command line switches but couldn't figure that part out. When I ran my fake-nasm generated 1.0.2 snapshot 64-bit OpenSSL code through the SDE (while AVX/AVX2 seemed to be on) it said all tests passed. But I think I'd like to see it on something "real"! On Fri, Mar 7, 2014 at 4:19 AM, Andy Polyakov <ap...@openssl.org> wrote: > > Quick question on 1.0.2 and Visual Studio win64 builds ... is ml64 > > supported or just nasm? > > Quick answer: quantum mechanics. Longer answer: state is unknown till > it's measured. Long answer: reports are not rejected, but > when-in-doubt-use-nasm principle applies, and reaction to reports can as > well be avoiding problem. > > As for supporting MASM in more general terms. You have to do better than > "it's *nice* to have MASM". You have to show why is it so, what is it > MASM offers that NASM doesn't. Even if there are some/any, they would be > weighed against advantages NASM has to offer (such as unconditional > availability for immediate download, possibility to affect the > functionality, cross-platform support). And even then faking nasm is > hardly appropriate way to solve the problem. > > >> While I am able to build those versions and they pass the "ms\test", I > >> do not have a CPU with Intel® AVX, Intel® AVX2, Intel® AVX-512 ... > >> anybody want to test it on those processors? :-) > > > http://software.intel.com/en-us/articles/intel-software-development-emulator/ > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org > -- Steve Kneizys Senior Business Process Engineer Voice: (610) 256-1396 [For Emergency Service (888)864-3282] Ferrilli Information Group -- Quality Service and Solutions for Higher Education web: http://www.ferrilli.com/ <http://www.figsolutions.com/> Making you a success while exceeding your expectations.
