Displaying 6 results from an estimated 6 matches for "getcastinstrcost".
2013 Jan 11
2
[LLVMdev] ARM vectorizer cost model
...dled
> 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 operations
> gets lowered.
>
BasicTTI::getCastInstrCost() assumes that they're free, which is probably
so that it returns something that doesn't break the cost model.
I can see the X86 table in X86TTI::getCastInstrCost(), are you expecting
something similar? I shall investigate all possible combinations and try to
build a similar model.
That a...
2016 Apr 11
2
X86 TRUNCATE cost for AVX & AVX2 mode
Hi,
I was going through the X86TTIImpl::getCastInstrCost, and got a doubt on cost
calculation for TRUNCATE instruction in AVX mode.
In AVX2ConversionTbl & AVXConversionTbl table there is no cost defined for
TRUNCATE v16i32 to v16i8, as a fallback it goes to SSE41ConversionTbl table and there
it finds cost as 30 for this operation. 30 cost for this o...
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 11
0
[LLVMdev] ARM vectorizer cost model
...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 operations gets lowered.
>
> BasicTTI::getCastInstrCost() assumes that they're free, which is probably so that it returns something that doesn't break the cost model.
>
> I can see the X86 table in X86TTI::getCastInstrCost(), are you expecting something similar? I shall investigate all possible combinations and try to build a similar mode...
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
2016 Apr 12
2
X86 TRUNCATE cost for AVX & AVX2 mode
...l.com>>; Zuckerman, Michael <michael.zuckerman at intel.com<mailto:michael.zuckerman at intel.com>>
Cc: llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>
Subject: X86 TRUNCATE cost for AVX & AVX2 mode
Hi,
I was going through the X86TTIImpl::getCastInstrCost, and got a doubt on cost
calculation for TRUNCATE instruction in AVX mode.
In AVX2ConversionTbl & AVXConversionTbl table there is no cost defined for
TRUNCATE v16i32 to v16i8, as a fallback it goes to SSE41ConversionTbl table and there
it finds cost as 30 for this operation. 30 cost for this o...