Displaying 4 results from an estimated 4 matches for "minimum_dependence_dist".
2014 Aug 28
2
[LLVMdev] Proposal for ""llvm.mem.vectorize.safelen"
...'d be curious to see proposed designs. I haven't explored the limits of LLVM's metadata format. For instance, what's the best way to store a distance matrix as metadata?
- I agree with Hal's request that we don't use the name 'safelen'
I'm fine with the "minimum_dependence_distance" if everyone else is.
- Arch
-----Original Message-----
From: Humphreys, Jonathan [mailto:j-humphreys at ti.com]
Sent: Wednesday, August 27, 2014 5:37 PM
To: Robison, Arch; Hal Finkel; Renato Golin; Alexander Musman (alexander.musman at gmail.com)
Cc: LLVM Dev
Subject: RE: [LLVMdev] Pro...
2014 Aug 28
2
[LLVMdev] Proposal for ""llvm.mem.vectorize.safelen"
...'d be curious to see proposed designs. I haven't explored the limits of LLVM's metadata format. For instance, what's the best way to store a distance matrix as metadata?
- I agree with Hal's request that we don't use the name 'safelen'
I'm fine with the "minimum_dependence_distance" if everyone else is.
- Arch
-----Original Message-----
From: Humphreys, Jonathan [mailto:j-humphreys at ti.com]
Sent: Wednesday, August 27, 2014 5:37 PM
To: Robison, Arch; Hal Finkel; Renato Golin; Alexander Musman (alexander.musman at gmail.com)
Cc: LLVM Dev
Subject: RE: [LLVMdev] Pro...
2014 Sep 28
2
[LLVMdev] Proposal for ""llvm.mem.vectorize.safelen"
...designs. I haven't explored the limits of LLVM's metadata
> format. For instance, what's the best way to store a distance matrix
> as metadata?
>
> - I agree with Hal's request that we don't use the name 'safelen'
>
> I'm fine with the "minimum_dependence_distance" if everyone else is.
>
> - Arch
>
> -----Original Message-----
> From: Humphreys, Jonathan [mailto:j-humphreys at ti.com]
> Sent: Wednesday, August 27, 2014 5:37 PM
> To: Robison, Arch; Hal Finkel; Renato Golin; Alexander Musman
> (alexander.musman at gmail...
2014 Aug 21
2
[LLVMdev] Proposal for ""llvm.mem.vectorize.safelen"
Here's an attempt to nail down the annotation semantics with support for respecting forward lexical dependences.
Each load, store, call, or invoke instruction can be labeled with !llvm.mem.vector_loop_access, which has two operands:
* The first operand is an integer denoting lexical position. The positions need not be consecutive, and may contain duplicates.
* The second operand is the