Re:GCC undefined behaviors are getting wild
by afiori on Monday November 28, 2022 @04:08AM
(#33771318)
I don't think this is a fair comparison as this is all based on implicit inferences by the compiler.
If the programmer had specifically invoked the "__assert_valid_pointer(p)" standard function (which does not exists) to promise the compile that the pointer was valid then it would be fine.
The problem is that there are a lot of places where the compiler makes these assumptions.
If the programmer had specifically invoked the "__assert_valid_pointer(p)" standard function (which does not exists) to promise the compile that the pointer was valid then it would be fine.
The problem is that there are a lot of places where the compiler makes these assumptions.