Displaying 2 results from an estimated 2 matches for "r270559".
2017 Mar 29
7
Well-formed @llvm.lifetime.start and @llvm.lifetime.end intrinsics
...d is not dominated by the corresponding
llvm.lifetime.start. As far as I understand the documentation [1] this
is a valid construction, meaning that the value of var is only
undefined before some point when c is true. I don't expect the
compiler to exploit this.
However, this miscompiles since r270559 ("Rework/enhance stack
coloring data flow analysis", https://reviews.llvm.org/D18827)
I modified Polly's code generator to produce
if (c) {
llvm.lifetime.start(&var)
} else {
llvm.lifetime.start(&var)
}
[...]
llvm.lifetime.end(&var)
and i...
2016 May 30
0
LLVM Weekly - #126, May 30th 2016
...committed. This describes how to build a JIT using ORC.
[r270487](http://reviews.llvm.org/rL270487),
[r271054](http://reviews.llvm.org/rL271054).
* LLVM's stack colouring analysis data flow analysis has been rewritten in
order to increase the number of stack variables that can be overlapped.
[r270559](http://reviews.llvm.org/rL270559).
* Parts of EfficiencySanitizer are starting to land, notably instrumentation
for its working set tool. [r270640](http://reviews.llvm.org/rL270640).
* SelectionDAG learned how to expand multiplication for larger integer types
where there isn't a standard run...