search for: amdil

...include/llvm/ADT/Triple.h =================================================================== --- include/llvm/ADT/Triple.h (revision 212686) +++ include/llvm/ADT/Triple.h (working copy) @@ -76,7 +76,8 @@ le32, // le32: generic little-endian 32-bit CPU (PNaCl / Emscripten) amdil, // amdil: amd IL spir, // SPIR: standard portable IR for OpenCL 32-bit version - spir64 // SPIR: standard portable IR for OpenCL 64-bit version + spir64, // SPIR: standard portable IR for OpenCL 64-bit version + kalimba // Kalimba: generic kalimba };...

Here is a patch for LLVM 2.9 that adds AMDIL as a valid target triple to LLVM. I'll get an updated patch for LLVM TOT if this doesn't patch cleanly next. Micah -------------- next part -------------- A non-text attachment was scrubbed... Name: AMDIL_OpenSource.patch Type: application/octet-stream Size: 1488 bytes Desc: AMDIL_OpenSour...

I am proud to announce that AMD is Open Sourcing AMDIL Code Generator for LLVM 2.9. While this version is not for uptake into LLVM mainline, it does build and is compatible with LLVM 2.9. This is the first step of the process, so I know there will be issues that show up. In the next few months, we will be providing more unit tests and an LLVM 3.0 comp...

...found in this git repository: http://cgit.freedesktop.org/~tstellar/llvm/ in the r600-initial-review branch or if you prefer you can download the entire tree with this link: http://cgit.freedesktop.org/~tstellar/llvm/snapshot/llvm-r600-initial-review.tar.gz The R600 backend is located in lib/Target/AMDIL First, a brief description of the backend: The r600 backend is being developed as a part of the Open Source compute stack in Mesa (http://www.mesa3d.org/), which uses the Gallium API. It uses large portions of the AMDIL backend which was open-sourced last December and you'll notice the Target...

The AMDIL Target needs new dwarf tokens for dwarf debug support, I'd we should handle this best? (which numbers to use for the new tokens): Two new tokens will be added: DW_AT_AMDIL_address_space (currently 0x3ff1) : needed in order to know which address space to read data from DW_AT_AMDIL_resource (cur...

...t a minimum of 3 different LLVM versions with our backend… LLVM TOT, the LLVM version used for AMD's OpenCL as shipped for Windows and Linux, and the LLVM version used for Apple's OpenCL as shipped for Mac OS… all different today and for the foreseeable future. Between the time that we get AMDIL "in" to llvm.org and the time that the other platforms using AMDIL are up to the level of LLVM at that initial check-in, we'll need to have conditional code in AMDIL. Thanks, Richard

Eric, Once both AMD and Apple have advanced their respective internal LLVM versions past the point where AMDIL went in to LLVM TOT, then we can rip out all the conditional code and just have the one LLVM TOT. This is about managing the transition to that utopia… ;-) Until then, the choices really come down to having support for multiple LLVM versions in TOT, or having multiple backends. The problem...

...ndex: include/llvm/ADT/Triple.h =================================================================== --- include/llvm/ADT/Triple.h (revision 212519) +++ include/llvm/ADT/Triple.h (working copy) @@ -76,24 +76,9 @@ le32, // le32: generic little-endian 32-bit CPU (PNaCl / Emscripten) amdil, // amdil: amd IL spir, // SPIR: standard portable IR for OpenCL 32-bit version - spir64 // SPIR: standard portable IR for OpenCL 64-bit version + spir64, // SPIR: standard portable IR for OpenCL 64-bit version + kalimba // Kalimba: generic kalimba }; - e...

Tom, Two things. One is missing tests. I have some I could send you, but they are mainly OpenCL based for the AMDIL backend, not for the R600. That brings me to the second thing. Are the AMDIL backend and the R600 backend the same, or not? At this point, they really do feel like they are separate back ends, with one dependent on the other. As there is no other backend that is dependent on another backend in t...

Please always make patches against TOT: http://llvm.org/docs/DeveloperPolicy.html#patches -Tanya On Aug 17, 2011, at 8:29 AM, Villmow, Micah wrote: > Here is a patch for LLVM 2.9 that adds AMDIL as a valid target triple to LLVM. > I'll get an updated patch for LLVM TOT if this doesn't patch cleanly next. > > Micah > <AMDIL_OpenSource.patch>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://...

Shajrawi, Yousef wrote: > > > The AMDIL Target needs new dwarf tokens for dwarf debug support, I’d we > should handle this best? (which numbers to use for the new tokens): > > Two new tokens will be added: > > DW_AT_AMDIL_address_space (currently 0x3ff1) : needed in order to know > which address space to read data from...

On 7/9/14, 12:33 PM, Eric Christopher wrote: > Any reason why you deleted code that isn't related? > > -eric > >> - enum SubArchType { >> - NoSubArch, >> - >> - ARMSubArch_v8, >> - ARMSubArch_v7, >> - ARMSubArch_v7em, >> - ARMSubArch_v7m, >> - ARMSubArch_v7s, >> - ARMSubArch_v6, >> -

...nt LLVM versions with our backend… LLVM TOT, the LLVM version used > for AMD's OpenCL as shipped for Windows and Linux, and the LLVM version > used for Apple's OpenCL as shipped for Mac OS… all different today and for > the foreseeable future. > > Between the time that we get AMDIL "in" to llvm.org and the time that the > other platforms using AMDIL are up to the level of LLVM at that initial > check-in, we'll need to have conditional code in AMDIL. > > Thanks, > Richard > > _______________________________________________ > LLVM Developer...

On Fri, Dec 07, 2012 at 08:58:21PM +0000, Relph, Richard wrote: > Eric, > Once both AMD and Apple have advanced their respective internal LLVM versions past the point where AMDIL went in to LLVM TOT, then we can rip out all the conditional code and just have the one LLVM TOT. This is about managing the transition to that utopia… ;-) > Until then, the choices really come down to having support for multiple LLVM versions in TOT, or having multiple backends. > Th...

On Mon, Mar 26, 2012 at 01:22:01PM -0400, Villmow, Micah wrote: > Tom, > Two things. One is missing tests. I have some I could send you, but they are mainly OpenCL based for the AMDIL backend, not for the R600. > I've started working on the tests, and I've pushed a few up to my llvm repo. I can add the AMDIL tests too if you want to send them. I think they will be helpful. > That brings me to the second thing. Are the AMDIL backend and the R600 backend the sam...

...y to use the backend to produce loadable > > compute kernels for the proprietary drivers, or on Mac/windows? > > > > Right, this is not currently possible. [Villmow, Micah] This is not possible with the R600 code generator, yes, but it is possible with some ELF fiddling with the AMDIL code generator which the R600 is based on. > > -Tom > > > > > > > Let me know if you have any other questions. > > > > > > -Tom > > > > > > [1] http://www.mesa3d.org/ > > > > > > > On Tue, Apr 24, 2012 at 2:52 PM,...

...//cgit.freedesktop.org/~tstellar/llvm/ in the r600-initial-review > > branch or if you prefer you can download the entire tree with this link: > > > http://cgit.freedesktop.org/~tstellar/llvm/snapshot/llvm-r600-initial-review.tar.gz > > The R600 backend is located in lib/Target/AMDIL > > > > First, a brief description of the backend: > > > > The r600 backend is being developed as a part of the Open Source compute > > stack in Mesa (http://www.mesa3d.org/), which uses the Gallium API. > > It uses large portions of the AMDIL backend which was o...

Is there a version of the AMDIL back-end that is compatible with LLVM 3.0/3.1? On Tue, May 29, 2012 at 8:33 AM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > > > > -----Original Message----- > > From: Stellard, Thomas > > Sent: Monday, May 28, 2012 9:07 AM > > To: Justin Holewinski > &...

...pository: > http://cgit.freedesktop.org/~tstellar/llvm/ in the r600-initial-review > branch or if you prefer you can download the entire tree with this link: > http://cgit.freedesktop.org/~tstellar/llvm/snapshot/llvm-r600-initial-review.tar.gz > The R600 backend is located in lib/Target/AMDIL > > First, a brief description of the backend: > > The r600 backend is being developed as a part of the Open Source compute > stack in Mesa (http://www.mesa3d.org/), which uses the Gallium API. > It uses large portions of the AMDIL backend which was open-sourced > last Decemb...

...pository: > http://cgit.freedesktop.org/~tstellar/llvm/ in the r600-initial-review > branch or if you prefer you can download the entire tree with this link: > http://cgit.freedesktop.org/~tstellar/llvm/snapshot/llvm-r600-initial-review.tar.gz > The R600 backend is located in lib/Target/AMDIL > > First, a brief description of the backend: > > The r600 backend is being developed as a part of the Open Source compute > stack in Mesa (http://www.mesa3d.org/), which uses the Gallium API. > It uses large portions of the AMDIL backend which was open-sourced > last Decemb...