Displaying 2 results from an estimated 2 matches for "getaddrofpointer".
2011 Dec 03
1
[LLVMdev] New strict-aliasing warning?
...nux/ppc64, I now see a warning
that I don't remember seeing previously:
llvm[2]: Compiling InlineSpiller.cpp for Release+Asserts build
/src/llvm-trunk-dev/include/llvm/ADT/PointerIntPair.h: In member
function ‘const PointerTy* llvm::PointerIntPair<PointerTy, IntBits,
IntType, PtrTraits>::getAddrOfPointer() const [with PointerTy = void*,
unsigned int IntBits = 1u, IntType = bool, PtrTraits =
llvm::PointerUnionUIntTraits<llvm::VNInfo*,
llvm::SmallVector<llvm::VNInfo*, 4u>*>]’:
/src/llvm-trunk-dev/include/llvm/ADT/PointerUnion.h:153: instantiated
from ‘const PT1* llvm::PointerUnion<PT...
2018 Apr 05
1
llvm::PointerIntPair -- is this by design or a bug?
I do agree that sign-extension is the right thing to do. Unlike bit-fields, llvm::PointerIntPair has asserts checking that the int value is within range. So if you assign an out of range value, it should fail with an assertion:
llvm::PointerIntPair<SomeType*, 3, int> pip;
pip.setInt(7); // can be made to fail as the valid range
// of signed 3-bit values is [-4:3]
The above