[PATCH] D63703: [stack-safety] Refactoring StackSafetyAnalysis to be accsessible from other passes

[Gilang Hamidy via llvm-commits]

Hi, thanks for the response.

We are currently planning to utilize StackSafetyAnalysis for memory
protection schemes that continue our prior work on ARM pointer
authentication (https://arxiv.org/abs/1811.09189).

Since the code seems to be dormant around 6 months, and I haven’t found
recent discussion regarding this, I thought that I can suggest some
refactoring so other users can use this analysis in other passes, similar
with the rest of LLVM analyses suites (e.g., alias analysis).

This is also to avoid changing the StackSafetyAnalysis code for every uses
by different users, which will be redundant. However, if some other
approach there is already an internal development to improve its API that
the public currently does not know of, this changes can be dropped.

Right now we plan to use the exposed objects to identify stack-allocated
variable which has out-of-bound access and use the information in our
memory protection scheme.

Regards,
Gilang


On Mon, Jun 24, 2019, 11:18 PM Vlad Tsyrklevich via Phabricator <
reviews at reviews.llvm.org> wrote:

> vlad.tsyrklevich added a subscriber: kcc.
> vlad.tsyrklevich added a comment.
>
> Hi gilang, out of curiosity what is your intended use of the
> StackSafetyAnalysis? Is it necessary to expose all of the information
> exposed here?
>
>
> Repository:
>   rG LLVM Github Monorepo
>
> CHANGES SINCE LAST ACTION
>   https://reviews.llvm.org/D63703/new/
>
> https://reviews.llvm.org/D63703
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20190625/99902459/attachment.html>