Displaying 3 results from an estimated 3 matches for "_mscv_ver".
Did you mean:
_msc_ver
2020 Jan 15
2
[tablegen] table readability / performance
...affected.
>
> One *could* make the tablegen behavior conditional on the compiler, and
> generate the character arrays for VS, and strings for other compilers.
> It
> has the potential to create MSVC only issues, but it seems harmless
> enough...
I can't see any current `#ifdef _MSCV_VER` usage in tablegen but I'm happy to
besmirch it for this.
--
Codeplay Software Ltd.
Company registered in England and Wales, number: 04567874
Registered office: Regent House, 316 Beulah Hill, London, SE19 3HF
2020 Jan 15
2
[tablegen] table readability / performance
...compiler, and
> > generate the character arrays for VS, and strings for other
> compilers.
> > It
> > has the potential to create MSVC only issues, but it seems
> harmless
> > enough...
> I can't see any current `#ifdef _MSCV_VER` usage in tablegen but
> I'm happy to
> besmirch it for this.
>
>
> I think the cleanest way to do this would be to have a cl::opt to control
> how string tables are emitted, and then control the default with `#if
> defined(_MSC_VER) && !defined(__clan...
2020 Jan 15
2
[tablegen] table readability / performance
On Tue Jan 14, 2020 at 8:27 PM, Reid Kleckner wrote:
> I don't think there's any technical reason for the current structure.
Apparently
[this](https://docs.microsoft.com/en-us/cpp/cpp/compiler-limits?view=vs-2019)
is a thing.
This results in the following delight happening on Visual Studio 2015:
> fatal error C1091: compiler limit: string exceeds 65535 bytes in length
So maybe