Displaying 8 results from an estimated 8 matches for "private_memori".
Did you mean:
private_memory
2013 Aug 08
5
[LLVMdev] Address space extension
On Aug 7, 2013, at 6:38 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
> On 08/08/2013 03:16 AM, Pete Cooper wrote:
>>
>> On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
>>
>>> On 08/08/2013 02:02 AM, Justin Holewinski wrote:
>>>> This worries me a bit. This would introduce language-specific
2013 Aug 08
1
[LLVMdev] Address space extension
On Thu, Aug 08, 2013 at 08:05:33AM -0400, Justin Holewinski wrote:
> On Wed, Aug 7, 2013 at 9:52 PM, Pete Cooper <peter_cooper at apple.com> wrote:
>
> >
> > On Aug 7, 2013, at 6:38 PM, Michele Scandale <michele.scandale at gmail.com>
> > wrote:
> >
> > On 08/08/2013 03:16 AM, Pete Cooper wrote:
> >
> >
> > On Aug 7, 2013, at 5:12
2013 Aug 08
0
[LLVMdev] Address space extension
On 08/08/2013 03:52 AM, Pete Cooper wrote:
>> Why a backend should be responsible (meaning have knowledge) for a
>> mapping between high level address spaces and low level address spaces?
> Thats true. I’m thinking entirely from the persecutive of the backend
> doing CL/CUDA. But actually LLVM is language agnostic. That is still
> something the metadata could solve. The
2013 Aug 08
0
[LLVMdev] Address space extension
On Wed, Aug 7, 2013 at 9:52 PM, Pete Cooper <peter_cooper at apple.com> wrote:
>
> On Aug 7, 2013, at 6:38 PM, Michele Scandale <michele.scandale at gmail.com>
> wrote:
>
> On 08/08/2013 03:16 AM, Pete Cooper wrote:
>
>
> On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com>
> wrote:
>
> On 08/08/2013 02:02 AM, Justin
2013 Aug 08
1
[LLVMdev] Address space extension
On 08/08/2013 02:05 PM, Justin Holewinski wrote:
> On Wed, Aug 7, 2013 at 9:52 PM, Pete Cooper <peter_cooper at apple.com
> <mailto:peter_cooper at apple.com>> wrote:
>
>
> On Aug 7, 2013, at 6:38 PM, Michele Scandale
> <michele.scandale at gmail.com <mailto:michele.scandale at gmail.com>> wrote:
>
>> On 08/08/2013 03:16 AM, Pete
2013 Aug 08
0
[LLVMdev] Address space extension
On 08/08/2013 03:16 AM, Pete Cooper wrote:
>
> On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
>
>> On 08/08/2013 02:02 AM, Justin Holewinski wrote:
>>> This worries me a bit. This would introduce language-specific
>>> processing into SelectionDAG. OpenCL maps address spaces one way, other
>>> languages map them
2013 Aug 08
3
[LLVMdev] Address space extension
On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
> On 08/08/2013 02:02 AM, Justin Holewinski wrote:
>> This worries me a bit. This would introduce language-specific
>> processing into SelectionDAG. OpenCL maps address spaces one way, other
>> languages map them in other ways. Currently, it is the job of the
>> front-end to map
2013 Aug 08
4
[LLVMdev] Address space extension
On Aug 7, 2013, at 7:23 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
> On 08/08/2013 03:52 AM, Pete Cooper wrote:
>>> Why a backend should be responsible (meaning have knowledge) for a
>>> mapping between high level address spaces and low level address spaces?
>> Thats true. I’m thinking entirely from the persecutive of the backend
>> doing