Displaying 6 results from an estimated 6 matches for "pointerintpairinfo".
2019 Sep 03
2
SourceMgr vs EXPENSIVE_CHECKS
...__debug::vector<unsigned int, std::allocator<unsigned int> >*,
std::__debug::vector<long unsigned int, std::allocator<long unsigned
int> >*>::NumLowBitsAvailable’:
/home/jayfoad2/git/llvm-project/llvm/include/llvm/ADT/PointerIntPair.h:144:48:
required from ‘struct llvm::PointerIntPairInfo<void*, 2,
llvm::pointer_union_detail::PointerUnionUIntTraits<std::__debug::vector<unsigned
char, std::allocator<unsigned char> >*, std::__debug::vector<short
unsigned int, std::allocator<short unsigned int> >*,
std::__debug::vector<unsigned int, std::allocator<un...
2019 Sep 03
2
SourceMgr vs EXPENSIVE_CHECKS
...::allocator<unsigned int> >*,
>> std::__debug::vector<long unsigned int, std::allocator<long unsigned
>> int> >*>::NumLowBitsAvailable’:
>> /home/jayfoad2/git/llvm-project/llvm/include/llvm/ADT/PointerIntPair.h:144:48:
>> required from ‘struct llvm::PointerIntPairInfo<void*, 2,
>> llvm::pointer_union_detail::PointerUnionUIntTraits<std::__debug::vector<unsigned
>> char, std::allocator<unsigned char> >*, std::__debug::vector<short
>> unsigned int, std::allocator<short unsigned int> >*,
>> std::__debug::vector&l...
2019 Oct 02
2
SourceMgr vs EXPENSIVE_CHECKS
...*,
>> >> std::__debug::vector<long unsigned int, std::allocator<long unsigned
>> >> int> >*>::NumLowBitsAvailable’:
>> >> /home/jayfoad2/git/llvm-project/llvm/include/llvm/ADT/PointerIntPair.h:144:48:
>> >> required from ‘struct llvm::PointerIntPairInfo<void*, 2,
>> >> llvm::pointer_union_detail::PointerUnionUIntTraits<std::__debug::vector<unsigned
>> >> char, std::allocator<unsigned char> >*, std::__debug::vector<short
>> >> unsigned int, std::allocator<short unsigned int> >*,
>...
2020 Jul 26
2
[LAA] RtCheck on pointers of different address spaces.
...5:15
llvm::RuntimeCheckingPtrGroup::addPointer(unsigned int) $SRC/llvm-project/llvm/lib/Analysis/LoopAccessAnalysis.cpp:292:15
llvm::RuntimePointerChecking::groupChecks(llvm::EquivalenceClasses<llvm::PointerIntPair<llvm::Value*, 1u, bool, llvm::PointerLikeTypeTraits<llvm::Value*>, llvm::PointerIntPairInfo<llvm::Value*, 1u, llvm::PointerLikeTypeTraits<llvm::Value*> > > >&, bool) $SRC/llvm-project/llvm/lib/Analysis/LoopAccessAnalysis.cpp:413:13
llvm::RuntimePointerChecking::generateChecks(llvm::EquivalenceClasses<llvm::PointerIntPair<llvm::Value*, 1u, bool, llvm::PointerLik...
2020 Jul 26
2
[LAA] RtCheck on pointers of different address spaces.
...5:15
llvm::RuntimeCheckingPtrGroup::addPointer(unsigned int) $SRC/llvm-project/llvm/lib/Analysis/LoopAccessAnalysis.cpp:292:15
llvm::RuntimePointerChecking::groupChecks(llvm::EquivalenceClasses<llvm::PointerIntPair<llvm::Value*, 1u, bool, llvm::PointerLikeTypeTraits<llvm::Value*>, llvm::PointerIntPairInfo<llvm::Value*, 1u, llvm::PointerLikeTypeTraits<llvm::Value*> > > >&, bool) $SRC/llvm-project/llvm/lib/Analysis/LoopAccessAnalysis.cpp:413:13
llvm::RuntimePointerChecking::generateChecks(llvm::EquivalenceClasses<llvm::PointerIntPair<llvm::Value*, 1u, bool, llvm::PointerLik...
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