Breaking changes in Visual C++ 2015

[deadalnix via Digitalmars-d]

On Sunday, 10 May 2015 at 12:54:02 UTC, Timon Gehr wrote:
> On 05/10/2015 07:39 AM, H. S. Teoh via Digitalmars-d wrote:
>> I also just realized that on Posix the profiling code 
>> apparently relies
>> on the rdtsc instruction, which counts CPU cycles in a 64-bit 
>> counter --
>> given the high frequencies of modern CPUs, moderately 
>> long-running
>> CPU-intensive processes easily overflow this counter, leading 
>> to
>> wrapped-around timing values and completely garbled output.
>>
>> gprof, for all of its flaws, does not suffer from this problem.
>
> http://www.wolframalpha.com/input/?i=2^64%2F%289+GHz%29
>
> What am I missing?

http://www.wolframalpha.com/input/?i=2^32%2F%289+GHz%29

It doesn't look at good that way, especially if you have some 
tight loops.