Displaying 3 results from an estimated 3 matches for "pseudoabort".
Did you mean:
pseudo_abort
2016 Jun 12
2
Early CSE clobbering llvm.assume
What he said :)
It also, representationally, has a related issue our current assume does
in terms of figuring out the set of assumptions applied. Given an
instruction, in extended SSA, because " assume" produces a value used by
things, it's trivial to find the chain of assumptions you can use for it.
In a straight control flow representation, it requires finding which side
of the
2016 Jun 14
3
Early CSE clobbering llvm.assume
...ely one of the reasons i'm proposing we've gotten it wrong.
>
>
> 2. “assert” takes advantage of this by being translated into if-then logic
> early on in the compilation
>
>
>
> 3. “assume” should also take advantage of this the same way. (generate a
> call to “pseudoabort” which
>
> At some late stage gets deleted)
>
This would fix precisely nothing, because of the above.
>
>
> Sanjoy’s argument is faulty, if it were true we would also find our
> handling of “assert” to be unacceptable
>
> but this is not the case, no one is arguing th...
2016 Jun 14
4
Early CSE clobbering llvm.assume
...compiler know how to do this.
This is precisely one of the reasons i'm proposing we've gotten it wrong.
2. “assert” takes advantage of this by being translated into if-then logic early on in the compilation
3. “assume” should also take advantage of this the same way. (generate a call to “pseudoabort” which
At some late stage gets deleted)
This would fix precisely nothing, because of the above.
Sanjoy’s argument is faulty, if it were true we would also find our handling of “assert” to be unacceptable
but this is not the case, no one is arguing that we need to re-design “assert”
Sure, but no...