Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-27 Thread Andy Polyakov
>>> How about something like this.. A VC-WIN32-XP target that has >>> everything needed to make a max compatibility target >>> When building under VS2012 and above.. (I also tested in VS2015) >>> adds CFLAGS /arch:IA32 -D_USING_V110_SDK71_ >>> adds BIN_LDFLAGS=/subsystem:console,5.01 /opt:ref >> >

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Scott Ware
On Fri, Aug 26, 2016 at 5:43 PM, Andy Polyakov wrote: >> How about something like this.. A VC-WIN32-XP target that has >> everything needed to make a max compatibility target >> When building under VS2012 and above.. (I also tested in VS2015) >> adds CFLAGS /arch:IA32 -D_USING_V110_SDK71_ >> adds

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Andy Polyakov
> How about something like this.. A VC-WIN32-XP target that has > everything needed to make a max compatibility target > When building under VS2012 and above.. (I also tested in VS2015) > adds CFLAGS /arch:IA32 -D_USING_V110_SDK71_ > adds BIN_LDFLAGS=/subsystem:console,5.01 /opt:ref How about se

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Blumenthal, Uri - 0553 - MITLL
If you want to dedicate a target to /arch:ia32, I can’t object or complain. VC-WIN32-XP sounds like a good choice for that. -- Regards, Uri Blumenthal On 8/26/16, 17:27, "openssl-dev on behalf of Scott Ware" wrote: >On Fri, Aug 26, 2016 at 5:11 PM, Blumenthal, Uri - 0553 - MITLL > wrote: >> O

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Scott Ware
On Fri, Aug 26, 2016 at 5:11 PM, Blumenthal, Uri - 0553 - MITLL wrote: > On 8/26/16, 17:04, "openssl-dev on behalf of Andy Polyakov" > wrote: > >>So suggestion is to impose /arch:ia32 on all users. Well, I personally >>have lesser problem with that (as most most performance-critical >>assembly co

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Blumenthal, Uri - 0553 - MITLL
On 8/26/16, 17:04, "openssl-dev on behalf of Andy Polyakov" wrote: >So suggestion is to impose /arch:ia32 on all users. Well, I personally >have lesser problem with that (as most most performance-critical >assembly code paths will be compiled anyway, processor capabilities >detected at run-time,

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Andy Polyakov
>> When building with Visual Studio 2008 SSE is disabled by default. When >> building with Visual Studio 2012 and above you must supply a new flag >> /arch:IA32 to not build with SSE. Would it be acceptable to update the >> Configure process to add the /arch:IA32 if Visual Studio 2012 or >> greater

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Richard Levitte
In message on Fri, 26 Aug 2016 14:31:57 -0400, Scott Ware said: wsware> On Fri, Aug 26, 2016 at 12:01 PM, Scott Ware wrote: wsware> > When building with Visual Studio 2008 SSE is disabled by default. When wsware> > building with Visual Studio 2012 and above you must supply a new flag wsware> >

Re: [openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Scott Ware
On Fri, Aug 26, 2016 at 12:01 PM, Scott Ware wrote: > When building with Visual Studio 2008 SSE is disabled by default. When > building with Visual Studio 2012 and above you must supply a new flag > /arch:IA32 to not build with SSE. Would it be acceptable to update the > Configure process to add t

[openssl-dev] Building VC-WIN32 with VS2012 and above breaks older CPU compatability

2016-08-26 Thread Scott Ware
When building with Visual Studio 2008 SSE is disabled by default. When building with Visual Studio 2012 and above you must supply a new flag /arch:IA32 to not build with SSE. Would it be acceptable to update the Configure process to add the /arch:IA32 if Visual Studio 2012 or greater is detected? T