Displaying 2 results from an estimated 2 matches for "type_max".
2013 Jun 07
0
[LLVMdev] NEON vector instructions and the fast math IR flags
...eflect that
What one could also do (but I don’t think is a good idea) is to just give floating point vector operations a max cost. You might run into unforeseen problems, including that other clients are generating vectorized LLVM IR.
(This makes we wonder whether we clamp the cost computation at TYPE_MAX :)
>
> cheers,
> --renato
2013 Jun 07
2
[LLVMdev] NEON vector instructions and the fast math IR flags
On 7 June 2013 15:41, Arnold Schwaighofer <aschwaighofer at apple.com> wrote:
> We don’t want to encode backend knowledge into the vectorizer (i.e. don’t
> vectorize type X because the backend does not support it).
>
We already do, via the cost table. This case is no different. It might not
be the best choice, but it is how the cost table is being built over the
last months.
The