Displaying 5 results from an estimated 5 matches for "grievejia".
2016 Aug 26
2
[GSoC] Final project report on CFL-AA
Dear LLVM devs,
My GSoC project this year is about alias analysis, and I wrote a short
article describing what I've done during the summer:
https://github.com/grievejia/GSoC2016/raw/master/writeup.pdf
In the report you can find an overview of what the current status of
CFL-AA. There are also some numbers in the end, but please take those
numbers with a grain of salt as they were rather preliminary. Like I
mentioned in the article, there are still *lots of* thi...
2018 Dec 18
2
Interprocedural AA
Hi,
I'm looking for interprocedural AAs and have, of course, found
https://llvm.org/docs/AliasAnalysis.html. However, the AAs that come
bundled with LLVM do not work interprocedurally in a way that I need it
(on/with stack variables). The two interesting looking AAs come with the
optional `poolalloc' module that hasn't been updated in years (I guess
2016 Aug 30
2
Fwd: cfl-aa
dear LLVMers,
I am trying to use some of the LLVM alias analyses, and I would like to
check two things with you: is scev-aa being maintained in LLVM 3.7? Second
question: I run cfl-aa, and I got a very small number of pointer
disambiguation (no alias) with it. My results for SPEC CINT 2006 follow
below. Is this low number of no alias responses something to be excepted?
Below the results that I
2016 Jul 31
2
Implementing Data Flow Integrity
Dear all,
I want to implement a pass that provides some kind of data flow
integrity similar to Write Integrity Testing
(https://www.doc.ic.ac.uk/~cristic/papers/wit-sp-ieee-08.pdf).
This approach statically determines for each memory write the
(conservative, overapproximated) points-to set of locations that can be
written by the instruction. Further, it instruments the memory write
instruction
2016 Aug 26
3
CFLAA
Hi David,
I am the one who's responsible for CFLAA's refactoring in the summer.
I've sent out another email on llvm-dev, and you can find more about my
work in my GSoC final report.
I think it is fantastic that you have done such an interesting work.
I'll definitely try to help getting the code reviewed and merged in the
current. After a quick glance at your patch, it seems