Displaying 4 results from an estimated 4 matches for "46eeps5h0e4".
2016 Mar 29
1
Memory scope proposal
...ntation of memory scopes in LLVM IR to
> allow more values than just the current two. The intention of this
> email is to invite comments on our proposal. There are some discussion
> before and it can be found here:
> https://groups.google.com/forum/#!searchin/llvm-dev/hsail/llvm-dev/46eEpS5h0E4/i3T9xw-DNVYJ
> <https://groups.google.com/forum/#%21searchin/llvm-dev/hsail/llvm-dev/46eEpS5h0E4/i3T9xw-DNVYJ>
>
> Here is our new proposal:
>
> =================================================================
> We still let the bitcode store memory scopes as "unsigne...
2016 Jan 28
6
Memory scope proposal
...to
enhance the representation of memory scopes in LLVM IR to allow more values
than just the current two. The intention of this email is to invite
comments on our proposal. There are some discussion before and it can be
found here:
https://groups.google.com/forum/#!searchin/llvm-dev/hsail/llvm-dev/46eEpS5h0E4/i3T9xw-DNVYJ
Here is our new proposal:
=================================================================
We still let the bitcode store memory scopes as *unsigned integers*, since
that is the easiest way to maintain compatibility. The values 0 and 1 are
special. All other values are meaningful onl...
2016 Mar 22
1
Memory scope proposal
...to
enhance the representation of memory scopes in LLVM IR to allow more values
than just the current two. The intention of this email is to invite
comments on our proposal. There are some discussion before and it can be
found here:
https://groups.google.com/forum/#!searchin/llvm-dev/hsail/llvm-dev/46eEpS5h0E4/i3T9xw-DNVYJ
Here is our new proposal:
=================================================================
We still let the bitcode store memory scopes as "unsigned integers", since
that is the easiest way to maintain compatibility. The values 0 and 1 are
special. All other values are mea...
2016 Apr 18
3
Memory scope proposal
...esentation of memory scopes in LLVM IR to allow more values
> than just the current two. The intention of this email is to invite
> comments on our proposal. There are some discussion before and it can be
> found here:
> https://groups.google.com/forum/#!searchin/llvm-dev/hsail/llvm-dev/46eEpS5h0E4/i3T9xw-DNVYJ
>
> Here is our new proposal:
>
> =================================================================
> We still let the bitcode store memory scopes as "unsigned integers", since
> that is the easiest way to maintain compatibility. The values 0 and 1 are
>...