Displaying 3 results from an estimated 3 matches for "d22547".
2016 Jul 21
4
RFC: Strong GC References in LLVM
...;
>>
>
> (Note, this list is stuff in the Scalar directory only. Everything in
> Vectorize would n eed it, etc)
>
> And in case folks want more evidence that reasonable llvm developers need
> something that just gives easy and right answers, see
> https://reviews.llvm.org/D22547 from just yesterday :)
>
> To move this along, i will go build the analysis (I already have it mostly
> done, actually). If someone updates our docs to make this stuff clear and
> obvious, that would be wonderful :)
>
> The analysis currently computes, internally, for a given BB:...
2016 Jul 21
2
RFC: Strong GC References in LLVM
...39;t take into account bugs, etc)
>
>
(Note, this list is stuff in the Scalar directory only. Everything in
Vectorize would n eed it, etc)
And in case folks want more evidence that reasonable llvm developers need
something that just gives easy and right answers, see
https://reviews.llvm.org/D22547 from just yesterday :)
To move this along, i will go build the analysis (I already have it mostly
done, actually). If someone updates our docs to make this stuff clear and
obvious, that would be wonderful :)
The analysis currently computes, internally, for a given BB:
EarliestLoadHoistBarrier (...
2016 Jul 21
3
RFC: Strong GC References in LLVM
> On Jul 21, 2016, at 7:45 AM, Philip Reames <listmail at philipreames.com> wrote:
>
> Joining in very late, but the tangent here has been interesting (if rather OT for the original thread).
>
> I agree with Danny that we might want to take a close look at how we model things like maythrow calls, no return, and other implicit control flow. I'm not convinced that moving