LLVM with the emscripten fastcomp javascript backend https://git.amat.us/emscripten-fastcomp/atom/test/CodeGen/NVPTX?h=master 2013-05-29T06:56:17Z 2013-05-29T06:56:17Z Bill Wendling isanbard@gmail.com 2013-05-29T06:56:17Z urn:sha1:89d9794d4925de2d64cb0c821e11189cd8372b05 ------------------------------------------------------------------------ r182394 | jholewinski | 2013-05-21 09:51:30 -0700 (Tue, 21 May 2013) | 1 line [NVPTX] Add @llvm.nvvm.sqrt.f() intrinsic ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_33@182829 91177308-0d34-0410-b5e6-96231b3b80d8 2013-05-29T06:55:34Z Bill Wendling isanbard@gmail.com 2013-05-29T06:55:34Z urn:sha1:afa582f1cd497d32f6c293cf50b08fefe0a2573f ------------------------------------------------------------------------ r182298 | jholewinski | 2013-05-20 09:42:18 -0700 (Mon, 20 May 2013) | 1 line [NVPTX] Fix mis-use of CurrentFnSym in NVPTXAsmPrinter. This was causing a symbol name error in the output PTX. ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_33@182828 91177308-0d34-0410-b5e6-96231b3b80d8 2013-05-29T06:54:20Z Bill Wendling isanbard@gmail.com 2013-05-29T06:54:20Z urn:sha1:b47f06ee6cbf04b3f3c456fc07a0c6a6ed1a6199 ------------------------------------------------------------------------ r182254 | jholewinski | 2013-05-20 05:13:32 -0700 (Mon, 20 May 2013) | 12 lines [NVPTX] Add GenericToNVVM IR converter to better handle idiomatic LLVM IR inputs This converter currently only handles global variables in address space 0. For these variables, they are promoted to address space 1 (global memory), and all uses are updated to point to the result of a cvta.global instruction on the new variable. The motivation for this is address space 0 global variables are illegal since we cannot declare variables in the generic address space. Instead, we place the variables in address space 1 and explicitly convert the pointer to address space 0. This is primarily intended to help new users who expect to be able to place global variables in the default address space. ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_33@182826 91177308-0d34-0410-b5e6-96231b3b80d8 2013-05-29T06:53:35Z Bill Wendling isanbard@gmail.com 2013-05-29T06:53:35Z urn:sha1:a12cd23d077639809201073b342dcc583021da38 ------------------------------------------------------------------------ r182253 | jholewinski | 2013-05-20 05:13:28 -0700 (Mon, 20 May 2013) | 1 line [NVPTX] Fix i1 kernel parameters and global variables. ABI rules say we need to use .u8 for i1 parameters for kernels. ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_33@182825 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-30T14:29:30Z Justin Holewinski jholewinski@nvidia.com 2013-03-30T14:29:30Z urn:sha1:b24fc1c7f7545362fe283730d5532fa7e7375c9e git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@178417 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-30T14:29:25Z Justin Holewinski jholewinski@nvidia.com 2013-03-30T14:29:25Z urn:sha1:21fdcb02716f5eae097abfd2f44e40563e90180a specific code paths. This allows us to write code like: if (__nvvm_reflect("FOO")) // Do something else // Do something else and compile into a library, then give "FOO" a value at kernel compile-time so the check becomes a no-op. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@178416 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-24T21:17:47Z Justin Holewinski jholewinski@nvidia.com 2013-03-24T21:17:47Z urn:sha1:1ce53cb526d23a3988fb12a5294ab1fcb2eb840f git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177847 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-20T00:10:32Z Justin Holewinski jholewinski@nvidia.com 2013-03-20T00:10:32Z urn:sha1:d73dc544f5e37e6d58befc71e57da3c132804543 A node's ordering is only propagated during legalization if (a) the new node does not have an ordering (is not a CSE'd node), or (b) the new node has an ordering that is higher than the node being legalized. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177465 91177308-0d34-0410-b5e6-96231b3b80d8 2013-02-12T14:18:49Z Justin Holewinski jholewinski@nvidia.com 2013-02-12T14:18:49Z urn:sha1:7eacad03efda36e09ebd96e95d7891cadaaa9087 Vectors were being manually scalarized by the backend. Instead, let the target-independent code do all of the work. The manual scalarization was from a time before good target-independent support for scalarization in LLVM. However, this forces us to specially-handle vector loads and stores, which we can turn into PTX instructions that produce/consume multiple operands. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@174968 91177308-0d34-0410-b5e6-96231b3b80d8 2013-02-11T18:56:35Z Justin Holewinski jholewinski@nvidia.com 2013-02-11T18:56:35Z urn:sha1:ff5adad9f39f60dc9f1caadef03b6aa7922ed168 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@174896 91177308-0d34-0410-b5e6-96231b3b80d8