Displaying 2 results from an estimated 2 matches for "cond_0".
Did you mean:
cond_t
2016 Jul 15
2
RFC: Strong GC References in LLVM
...et us
> basically implement a more precise version of (2).
>
>
>
> [0]: I may have (incorrectly) mentioned otherwise on IRC, but we need
> to model safety properties of stores as well, to avoid transforms
> like:
>
> %x = malloc() ;; known thread local
> if (cond_0) {
> store GCREF %val to %x
> }
> if (cond_1) {
> store i64 %val to %x
> }
>
> to
>
> %x = malloc() ;; known thread local
> if (cond_0 || cond_1) {
> store GCREF %val to %x ;; This "speculative" store is bad
> if (cond_1) {
&...
2016 Jul 14
5
RFC: Strong GC References in LLVM
Hi Andy,
Andrew Trick wrote:
>> But for the purposes of this discussion, only the legality (or lack
>> thereof) of the above transform matters, not whether it is profitable
>> or not.
>
> Given that you will need to disable the transform for GCRefs, it’s
interesting that if it’s only something that needs to run before ISEL
then you’re not actually losing any