Displaying 3 results from an estimated 3 matches for "gettargetcpu".
2014 Jun 17
3
[LLVMdev] Attaching range metadata to IntrinsicInst
...ue Wu <jingyue at google.com> wrote:
> Hi Eric,
>
> In the IR, besides "target datalayout" and "target triple", we have a
> special "target cpu" string which is set by the Clang front-end according to
> its -target-cpu flag. We also write a Module::getTargetCPU() method to
> retrieve this string from the IR.
>
Not sure that I like this. Each function can have a target cpu though.
That each subtarget cares about the value of the target cpu for how
the intrinsic works sounds a lot like TargetTransformInfo to me.
-eric
> Jingyue
>
>
> On...
2014 Jun 17
2
[LLVMdev] Attaching range metadata to IntrinsicInst
Eh? How do you envision this?
-eric
On Tue, Jun 17, 2014 at 2:09 PM, Jingyue Wu <jingyue at google.com> wrote:
> Hi Nick,
>
> That makes sense. I think a main issue here is that the ranges of these PTX
> special registers (e.g., threadIdx.x) depend on -target-cpu which is only
> visible to clang and llc. Would you mind we specify "target cpu" in the IR
> similar
2014 Jun 17
5
[LLVMdev] Attaching range metadata to IntrinsicInst
Chandler Carruth wrote:
> This seems fine to me, but I'd like to make sure it looks OK to Nick as
> well.
I strongly prefer baking in knowledge about the intrinsics themselves
into the passes if possible. Metadata will always be secondary.
Separately, should value tracking look use range metadata when it's
available? Absolutely.
I think it should apply to all CallInst not just