search for: twinsem

...se is an object LLVM can now about or not does? I see. That makes sense. The reason I restricted myself to offset 0 is that we'd like to do this without actually having any accessible objects anywhere, which works out if the objects have size 0. FWIW, in <https://people.mpi-sws.org/~jung/twinsem/twinsem.pdf> we anyway had to make "getelementptr inbounds" on integer pointers (pointers obtained by casting an integer to a pointer) never yield poison directly and instead defer the in-bound check to the time when the actual access happens. That nicely accommodates all uses of gete...

...f an allocated object" > > * I would argue every object needs to have an extend, hence cannot be > zero-sized. I would find that a rather surprising exception / special case. There's nothing wrong with objects of size 0. >> FWIW, in <https://people.mpi-sws.org/~jung/twinsem/twinsem.pdf> we anyway had to >> make "getelementptr inbounds" on integer pointers (pointers obtained by casting >> an integer to a pointer) never yield poison directly and instead defer the >> in-bound check to the time when the actual access happens. That nicely &g...

Hi Johannes, > From the Lang-Ref statement > > "With the inbounds keyword, the result value of the GEP is undefined > if the address is outside the actual underlying allocated object and > not the address one-past-the-end." > > I'd argue that the actual offset value (here 0) is irrelevant. The GEP > value is undefined if inbounds is present and the