Displaying 3 results from an estimated 3 matches for "a5a3c08a".
2009 Oct 09
0
[LLVMdev] Instructions that cannot be duplicated
On Thu, Oct 8, 2009 at 2:11 PM, Reid Kleckner <rnk at mit.edu> wrote:
> IMO Jeff's solution is the cleanest, simplest way to get code that
> works. Just generate a separate function for every barrier in the
> program, and mark it noinline. This way the instruction pointers will
> be unique to the barrier.
No, this gets rather nasty: to support an instruction like this, it
2009 Oct 09
3
[LLVMdev] Instructions that cannot be duplicated
...> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091008/a5a3c08a/attachment.html>
2009 Oct 08
3
[LLVMdev] Instructions that cannot be duplicated
On Thu, Oct 8, 2009 at 3:59 PM, Devang Patel <devang.patel at gmail.com> wrote:
> On Thu, Oct 8, 2009 at 11:28 AM, Villmow, Micah <Micah.Villmow at amd.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Jeffrey Yasskin [mailto:jyasskin at google.com]
>>> Sent: Thursday, October 08, 2009 11:09 AM
>>> To: Villmow, Micah