Displaying 4 results from an estimated 4 matches for "x86typeconversioncosttblentri".
Did you mean:
x86typeconversioncosttblentry
2013 Jan 11
2
[LLVMdev] ARM vectorizer cost model
On 10 January 2013 23:00, Nadav Rotem <nrotem at apple.com> wrote:
> Some of the costs for the arithmetic operations should be handled
> automatically by the BasicTTI (which asks TartetLowering if the type and
> operations are legal). We need to have cost tables for things like "trunk
> <4 x i64> to <4 x i8>" because even TLI does not know how custom
2013 Jan 11
0
[LLVMdev] ARM vectorizer cost model
On Jan 11, 2013, at 7:36 AM, Renato Golin Linaro <renato.golin at linaro.org> wrote:
> On 10 January 2013 23:00, Nadav Rotem <nrotem at apple.com> wrote:
> Some of the costs for the arithmetic operations should be handled automatically by the BasicTTI (which asks TartetLowering if the type and operations are legal). We need to have cost tables for things like "trunk <4 x
2013 Jan 10
0
[LLVMdev] ARM vectorizer cost model
On Jan 10, 2013, at 2:19 PM, Renato Golin Linaro <renato.golin at linaro.org> wrote:
> I'm also thinking about the individual instructions cost (getArithmeticInstrCost, getShuffleCost, etc). That can be a simple and easily parallelized task. I got the A9 manual that has the cost of all instructions (including NEON and VFP), that should give us a head start.
Renato,
Thanks for
2013 Jan 10
2
[LLVMdev] ARM vectorizer cost model
On 9 January 2013 17:10, Nadav Rotem <nrotem at apple.com> wrote:
> For example:
> "opt -cost-model -analyze dumper.ll -mtriple=thumbv7
> -mcpu=cortex-a15"
>
> I also run the vectorizer with -debug-only=loop-vectorize because it dumps
> the costs of all of the instructions with different vectorization factors,
> and it also detects the different kinds