Displaying 2 results from an estimated 2 matches for "checkforallinstructions".
2020 Mar 16
3
[GSOC] "Project: Improve inter-procedural analyses and optimisations"
...u see in the topmost updateImpl() that they're a bunch Opcodes.
Those are instructions (inside our function) that can potentially break our
initial assumption (e.g. call to a function that either we know it throws
or at least it is not guaranteed that it doesn't). In the updateImpl(),
using checkForAllInstructions, we loop through all those instructions and
call for each one the predicate CheckForNoUnwind. Note a couple of things:
- TEST 1 has no such instructions whatsoever so if you put a print inside
the predicate, you'll see nothing. - You can see that the predicate returns
a boolean value. If it'...
2020 Mar 14
3
[GSOC] "Project: Improve inter-procedural analyses and optimisations"
Hi Fahad,
> > Improve dynamic memory related capabilities of Attributor. For example
> Improve HeapToStackConversions. Maybe such deductions can help safety
> (dis)provers. For example, can we improve the use-after-free bug detection
> using some attributes?
> Stefan should know more about H2S. Regarding the use-after-free, I don't
> think there's currently any plans