Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] ATTN: PTX Back-End Users - EOL"
2013 Dec 09
1
[LLVMdev] PTX generation examples?
Ah, that's helpful. I knew that I'd need to end up with PTX as text, not a true binary, but I would have figured that it would come out of MCJIT. Thanks for helping to steer me away from the wrong trail.
OK, one more question: Can anybody clarify the pros and cons of generating the PTX through the standard LLVM distro, versus using the "libnvvm" that comes with the Cuda SDK?
2013 Dec 09
0
[LLVMdev] PTX generation examples?
There is no MCJIT support for PTX at the moment (mainly because PTX does
not have a binary format, and is not machine code per se).
To generate PTX at run-time, you just set up a standard codegen pass
manager like you would like an off-line compiler. The output will be a
string buffer that contains the PTX, which you can load into the CUDA
runtime.
As for determining if PTX support is compiled
2013 Jan 11
0
[LLVMdev] Update PTX section in CodeGenerator.html
Right, I forgot to update that originally. I also have a separate document
in the works that goes into more detail for NVPTX.
On Fri, Jan 11, 2013 at 2:57 AM, 陳韋任 (Wei-Ren Chen) <
chenwj at iis.sinica.edu.tw> wrote:
> Hi Justin,
>
> I believe the PTX section in the link below need some love,
> updating "lib/Target/PTX" to "lib/Target/NVPTX" for example.
2013 Feb 04
1
[LLVMdev] Problem with PTX assembly printing (NVPTX backend)
Hi Nikolaos,
Following commands work great for me.
$ clang -S -emit-llvm -target nvptx -x cl -include clc/clctypes.h
../data-types/scalar.cl
$ llc -mcpu=sm_30 scalar.s
You can follow Justin's blog [1]. It helped me a lot to understand where to
start.
[1] http://jholewinski.org/blog/llvm-3-0-ptx-backend/
Best,
Ankur
On Mon, Feb 4, 2013 at 11:40 PM, Justin Holewinski <
justin.holewinski
2013 Jan 11
1
[LLVMdev] Update PTX section in CodeGenerator.html
CodeGenerator updates committed.
On Fri, Jan 11, 2013 at 7:39 AM, Justin Holewinski <
justin.holewinski at gmail.com> wrote:
> Right, I forgot to update that originally. I also have a separate
> document in the works that goes into more detail for NVPTX.
>
>
> On Fri, Jan 11, 2013 at 2:57 AM, 陳韋任 (Wei-Ren Chen) <
> chenwj at iis.sinica.edu.tw> wrote:
>
>>
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On 11.01.2013, at 21:31, Justin Holewinski <justin.holewinski at gmail.com> wrote:
> On Fri, Jan 11, 2013 at 3:26 PM, Benjamin Kramer <benny.kra at gmail.com> wrote:
>
> On 11.01.2013, at 07:36, 陳韋任 (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> wrote:
>
> > Hi Pawel,
> >
> > PTX already be replaced with NVPTX. However, PTX subdirectory
> >
2013 Jan 11
1
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On 1/11/2013 7:15 AM, Justin Holewinski wrote:
> Removed from trunk. Pawel can decide if its necessary to update the
> tarballs.
>
> Thanks for the report! Apparently git-svn does not delete removed
> directories.
PTX directories still exists in release_32 branch and RELEASE_32/final.
But they are all empty so PTX can not be build.
>
>
> On Fri, Jan 11, 2013 at 1:36
2013 Jan 11
3
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On Fri, Jan 11, 2013 at 3:26 PM, Benjamin Kramer <benny.kra at gmail.com>wrote:
>
> On 11.01.2013, at 07:36, 陳韋任 (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw>
> wrote:
>
> > Hi Pawel,
> >
> > PTX already be replaced with NVPTX. However, PTX subdirectory
> > still sit in lib/Target in 3.2 release. Do you think update the
> > release tarball is
2013 Feb 04
0
[LLVMdev] Problem with PTX assembly printing (NVPTX backend)
Alright, couple of points here:
1. Address space 0 is invalid for global variables. This is causing a
crash in llc where we use llvm_unreachable() on this case. This is most
likely why you're seeing llc run forever. The fix for this is to use
address space 1 for globals, which puts them into PTX global memory. On
our side, we should provide a meaningful error message in this case.
2. The
2013 Feb 09
0
[LLVMdev] C-to-PTX compilation issues
The issue you're seeing is actually a problem with clang integration.
Generally, clang does not understand all of the conventions required by
the NVPTX back-end, and compilation from general C may not always work.
In this case, it's the local array "b" that is the problem. Clang pulls
this out into the global scope, but keeps it in address space 0. In the
back-end, address
2013 Jan 11
4
[LLVMdev] Update PTX section in CodeGenerator.html
Hi Justin,
I believe the PTX section in the link below need some love,
updating "lib/Target/PTX" to "lib/Target/NVPTX" for example.
Would you like to take a look?
http://llvm.org/docs/CodeGenerator.html#the-ptx-backend
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
2013 Feb 04
0
[LLVMdev] Problem with PTX assembly printing (NVPTX backend)
On Mon, Feb 4, 2013 at 10:46 AM, <nkavv at physics.auth.gr> wrote:
> Hi all,
>
> I'm trying to use the newly added (in LLVM 3.2) NVPTX backend for
> producing PTX (Parallel Thread eXecution) assembly from simple C programs.
>
> While using llc with -march for mips and x86 works, -march=nvptx doesn't
> work. This seems reasonable since I can see that the
>
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On 1/11/2013 2:40 PM, Brooks Davis wrote:
> On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer wrote:
>>
>> On 11.01.2013, at 21:31, Justin Holewinski
>> <justin.holewinski at gmail.com> wrote:
>>
>>> On Fri, Jan 11, 2013 at 3:26 PM, Benjamin Kramer
>>> <benny.kra at gmail.com> wrote:
>>>
>>> On 11.01.2013, at
2011 Mar 31
1
[LLVMdev] GSoC: PTX Back-End for LLVM
On Mon, Mar 28, 2011 at 10:19 PM, Tobias Grosser
<grosser at fim.uni-passau.de>wrote:
> On 03/28/2011 09:12 AM, Justin Holewinski wrote:
>
>> Hi All,
>>
>> I am going to submit a GSoC proposal for LLVM this year, and I would
>> like to first post it here to get constructive feedback before I submit
>> it before the April 8 deadline. This is the first
2013 Jan 11
5
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer wrote:
>
> On 11.01.2013, at 21:31, Justin Holewinski <justin.holewinski at gmail.com> wrote:
>
> > On Fri, Jan 11, 2013 at 3:26 PM, Benjamin Kramer <benny.kra at gmail.com> wrote:
> >
> > On 11.01.2013, at 07:36, ????????? (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> wrote:
> >
>
2013 Jan 11
2
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On Fri, Jan 11, 2013 at 3:47 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote:
> On 1/11/2013 2:40 PM, Brooks Davis wrote:
> > On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer wrote:
> >>
> >> On 11.01.2013, at 21:31, Justin Holewinski
> >> <justin.holewinski at gmail.com> wrote:
> >>
> >>> On Fri, Jan 11, 2013 at 3:26
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
On 1/11/2013 2:51 PM, Justin Holewinski wrote:
> On Fri, Jan 11, 2013 at 3:47 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote:
>
>> On 1/11/2013 2:40 PM, Brooks Davis wrote:
>>> On Fri, Jan 11, 2013 at 09:33:17PM +0100, Benjamin Kramer wrote:
>>>>
>>>> On 11.01.2013, at 21:31, Justin Holewinski
>>>> <justin.holewinski at
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
Removed from trunk. Pawel can decide if its necessary to update the
tarballs.
Thanks for the report! Apparently git-svn does not delete removed
directories.
On Fri, Jan 11, 2013 at 1:36 AM, 陳韋任 (Wei-Ren Chen) <
chenwj at iis.sinica.edu.tw> wrote:
> Hi Pawel,
>
> PTX already be replaced with NVPTX. However, PTX subdirectory
> still sit in lib/Target in 3.2 release. Do you
2013 Feb 04
2
[LLVMdev] Problem with PTX assembly printing (NVPTX backend)
Hi all,
I'm trying to use the newly added (in LLVM 3.2) NVPTX backend for
producing PTX (Parallel Thread eXecution) assembly from simple C
programs.
While using llc with -march for mips and x86 works, -march=nvptx
doesn't work. This seems reasonable since I can see that the
libLLVMNVPTXAsmPrinter.a library is about 500 bytes (thus empty).
However, the strange thing is that
2013 Feb 09
2
[LLVMdev] C-to-PTX compilation issues
Hi all,
i'm trying to compile some small ANSI C benchmarks to PTX assembly.
For this purpose, I'm using the NVPTX backend, introduced in the LLVM
3.2 release.
It appears that certain LLVM constructs cannot be compiled to PTX. The
problems mostly deal with handling of arrays. I also don't get any
debug info when these problems.
I use "llc" for compiling regular .ll