aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CreateInvocationFromCommandLine.cpp
diff options
context:
space:
mode:
authorNikita Popov <npopov@redhat.com>2022-06-10 17:18:33 +0200
committerNikita Popov <npopov@redhat.com>2022-06-13 10:45:55 +0200
commit2a3288776c940669fed430c3984b91e61ab0f015 (patch)
treefe36074995527d4ab18a80df71f3fbbfb144165e /clang/lib/Frontend/CreateInvocationFromCommandLine.cpp
parentdbac0e83d14cc3dcbb22af826ad550dfb6431a61 (diff)
downloadllvm-2a3288776c940669fed430c3984b91e61ab0f015.zip
llvm-2a3288776c940669fed430c3984b91e61ab0f015.tar.gz
llvm-2a3288776c940669fed430c3984b91e61ab0f015.tar.bz2
[InstSimplify] Update GEP test to use opaque pointers (NFC)
With opaque pointers, we end up merging these GEPs and dropping the inrange attribute (in the last two cases). This did not happen previously, because typed pointers use less powerful GEP folding logic. I'm a bit unsure whether this is something we need to be concerned about or not. I believe that generally our stance is that we should perform folds even if this requires losing poison-generating flags like inrange. We can either a) accept this as-is, b) try to inhibit folding if it requires dropping inrange or c) try to fold to poison if we know that inrange is going to be violated. For now, we accept it as-is. Differential Revision: https://reviews.llvm.org/D127503
Diffstat (limited to 'clang/lib/Frontend/CreateInvocationFromCommandLine.cpp')
0 files changed, 0 insertions, 0 deletions