Hello, time for an Undefined Behavior with context. The context is the XOR linked list, where a single integer is used to encode a forwards pointer and a backwards pointer. https://en.wikipedia.org/wiki/XOR_linked_list … #thread
I don't see any justification for a claim that the implementation-defined result of the conversion can blow up into undefined behavior. If uintptr_t exists, it must be round-trip pointer-preserving.
-
-
“pointer provenance” uintptr_t p = (uintptr_t)&x; while (p++ != (uintptr_t) &y); does not have to terminate and uintptr_t p = rand(); if (p == (uintptr_t) &y) *p = 1; does not have to do what you expect.
-
"Pointer provenance" is utter bullshit.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.