search for: randomascii

Anybody still has MSVC 2015 update 1? It seems that MSVC 2015U2 miscompiles stream_encoder_intrin_sse2.c, stream_encoder_intrin_ssse3.c (and probably stream_encoder_intrin_avx2.c, but currently I cannot test it 'cause I don't have avx2 CPU). I wonder what happened and what changed in the asm code that MSVC generates.

...lvm-dev < llvm-dev at lists.llvm.org> wrote: > Note that this is intentional from the MSVC C++ library implementation > side of things. For major versions, no attempt is made to preserve library > ABI compatibility. > I am aware of a language ABI break in VC++ 2013. > https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ > > I'm not currently aware of any on the VC++ 2015 side of things, but that > doesn't mean much. > > > On 9/7/2016 2:34 PM, Martin O'Riordan via llvm-dev wrote: > > Apart from the obvious lic...

...e that this is intentional from the MSVC C++ library implementation > >> side of things. For major versions, no attempt is made to preserve > library > >> ABI compatibility. > >> > >> I am aware of a language ABI break in VC++ 2013. > >> > https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ > >> > >> I'm not currently aware of any on the VC++ 2015 side of things, but that > >> doesn't mean much. > >> > >> > >> > >> On 9/7/2016 2:34 PM, Martin O&...

...e that this is intentional from the MSVC C++ library implementation > >> side of things. For major versions, no attempt is made to preserve > library > >> ABI compatibility. > >> > >> I am aware of a language ABI break in VC++ 2013. > >> > https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ > >> > >> I'm not currently aware of any on the VC++ 2015 side of things, but that > >> doesn't mean much. > >> > >> > >> > >> On 9/7/2016 2:34 PM, Martin O&...

...e: > > Note that this is intentional from the MSVC C++ library > implementation side of things. For major versions, no attempt > is made to preserve library ABI compatibility. > > I am aware of a language ABI break in VC++ 2013. > https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ > > I'm not currently aware of any on the VC++ 2015 side of > things, but that doesn't mean much. > > > On 9/7/2016 2:34 PM, Martin O'Riordan via llvm-dev wrote: >>...

...gt; llvm-dev at lists.llvm.org> wrote: > > Note that this is intentional from the MSVC C++ library implementation > side of things. For major versions, no attempt is made to preserve library > ABI compatibility. > > I am aware of a language ABI break in VC++ 2013. > https://randomascii.wordpress.com/2013/12/01/vc-2013-class- > layout-change-and-wasted-space/ > > I'm not currently aware of any on the VC++ 2015 side of things, but that > doesn't mean much. > > > > On 9/7/2016 2:34 PM, Martin O'Riordan via llvm-dev wrote: > > Apart from the...

...s is intentional from the MSVC C++ library implementation >> >> side of things. For major versions, no attempt is made to preserve library >> >> ABI compatibility. >> >> >> >> I am aware of a language ABI break in VC++ 2013. >> >> https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ <https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/> >> >> >> >> I'm not currently aware of any on the VC++ 2015 side of things, but that >> >&gt...

Apart from the obvious licencing issues, each time I have moved from one version of VC++ to another, the big problem I have had is not specifically the ABI at the register passing, stack organisation level, but rather the implementation details of the Standard C++ libraries, and in particular the STL containers. While the compiler team puts considerable effort into maintaining the ABI, the C++

...t;> wrote: >> >> Note that this is intentional from the MSVC C++ library implementation >> side of things. For major versions, no attempt is made to preserve library >> ABI compatibility. >> >> I am aware of a language ABI break in VC++ 2013. >> https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ >> >> I'm not currently aware of any on the VC++ 2015 side of things, but that >> doesn't mean much. >> >> >> >> On 9/7/2016 2:34 PM, Martin O'Riordan via llvm-dev wrote: &gt...

...e that this is intentional from the MSVC C++ library implementation > >> side of things. For major versions, no attempt is made to preserve > library > >> ABI compatibility. > >> > >> I am aware of a language ABI break in VC++ 2013. > >> > https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ > >> > >> I'm not currently aware of any on the VC++ 2015 side of things, but that > >> doesn't mean much. > >> > >> > >> > >> On 9/7/2016 2:34 PM, Martin O&...

...e that this is intentional from the MSVC C++ library implementation > >> side of things. For major versions, no attempt is made to preserve > library > >> ABI compatibility. > >> > >> I am aware of a language ABI break in VC++ 2013. > >> > https://randomascii.wordpress.com/2013/12/01/vc-2013-class-layout-change-and-wasted-space/ > >> > >> I'm not currently aware of any on the VC++ 2015 side of things, but that > >> doesn't mean much. > >> > >> > >> > >> On 9/7/2016 2:34 PM, Martin O&...

I think it's been a little over a year since we bumped the minimum VS version to 2013. Are we planning to do the same for 2015? Update 2 is releasing soon, which is stable enough at least to ship Chromium <https://randomascii.wordpress.com/2016/03/24/compiler-bugs-found-when-porting-chromium-to-vc-2015/> . Language wise, 2015 comes with a lot of new C++ features. The most interesting to people will probably be template aliases, C++11 constexpr, the thread_local keyword, and thread-safe function local statics (final...