Re: MIT discovered issue with gcc

2013-12-01 Thread Kurt Roeckx
On Sun, Dec 01, 2013 at 11:18:47PM +0900, Joel Rees wrote: > optimizer's excuse to silently kill undefined behavior code. As far as I know, all examples I have seen this is not what happens. What happens is that the compiler assumes you write code that has defined behavior and optimises based on

Re: MIT discovered issue with gcc

2013-12-01 Thread Joel Rees
On Sun, Dec 1, 2013 at 9:26 AM, Bernhard R. Link wrote: > * Joel Rees [131129 00:36]: >> The standard needs to be re-written to encourage sane behavior in >> undefined situations, and if you don't like that opinion, I'll take >> some time later, when I have some, to rip your arguments that I've >