tree 8524bb913a6b3e4f8d6d315d5e826417cabce0ef
parent 4ebecc164031228a8c36cddcf7af873ae62880ed
author Nikita Popov <nikita.ppv@gmail.com> 1605640269 +0100
committer Copybara-Service <copybara-worker@google.com> 1606742529 -0800

[AA] Split up LocationSize::unknown()

Currently, we have some confusion in the codebase regarding the
meaning of LocationSize::unknown(): Some parts (including most of
BasicAA) assume that LocationSize::unknown() only allows accesses
after the base pointer. Some parts (various callers of AA) assume
that LocationSize::unknown() allows accesses both before and after
the base pointer (but within the underlying object).

This patch splits up LocationSize::unknown() into
LocationSize::afterPointer() and LocationSize::beforeOrAfterPointer()
to make this completely unambiguous. I tried my best to determine
which one is appropriate for all the existing uses.

The test changes in cs-cs.ll in particular illustrate a previously
clearly incorrect AA result: We were effectively assuming that
argmemonly functions were only allowed to access their arguments
after the passed pointer, but not before it. I'm pretty sure that
this was not intentional, and it's certainly not specified by
LangRef that way.

Differential Revision: https://reviews.llvm.org/D91649

GitOrigin-RevId: 4df8efce80e373dd1e05bd4910c796a0c91383e7