Visual C++ 2015 error

[Robert Pope]

Sorry, I've been busy for a couple days and missed your reply. I just figured out the same thing.

[pijl]

There are some more issues with VS2015. I discovered that when it vectorizes loops with unsigned __int64 inside, it masks them to 32 bits. Took me a while to find that ...
In the end turning off optimization of that part (it was bitboard init code so that doesn't matter much anyway) solved that problem.

[jdart]

I disable console buffering this way (last 2 lines are for C++ iostream):

Code: Select all

   // Must use unbuffered console
    setbuf(stdin,NULL);
    setbuf(stdout, NULL);
    std::cout.rdbuf()->pubsetbuf(NULL, 0);
    std::cin.rdbuf()->pubsetbuf(NULL, 0);

--Jon

[mar]

If I comment out the setvbuf(), it works as expected, but then I am buffering input.

I can confirm this
Microsoft not only managed to break the compiler (see what Richard posted), they also managed to screw up CRT.
I'd recommend them to smoke less crack...

[Joost Buijs]

If I comment out the setvbuf(), it works as expected, but then I am buffering input.

I can confirm this
Microsoft not only managed to break the compiler (see what Richard posted), they also managed to screw up CRT.
I'd recommend them to smoke less crack...

I guess we have to wait for a service pack, it is a waste of time to work around the cracks.
Right now I'm using VS2013 update 5, which is more or less stable.
I like to develop under MSVC because it compiles very fast compared to Intel.

[Robert Pope]

If I comment out the setvbuf(), it works as expected, but then I am buffering input.

I can confirm this
Microsoft not only managed to break the compiler (see what Richard posted), they also managed to screw up CRT.
I'd recommend them to smoke less crack...

So, do we need to report this somewhere? I gave up and went back to VS 2013. I have little enough time to spend on my engine as it is.