search for: carrizo

...the new numbering system and generated from the new git repository at cgit.freedesktop.org/amd/hsakmt This release works with upstream amdkfd from kernel version 3.19 and above, although not all features are supported by all kernel versions. With regard to H/W, it supports AMD's Kaveri and Carrizo APU. Carrizo is supported only from kernel 4.2. Patches to hsakmt should be sent to dri-devel at lists.freedesktop.org. Bugs against this library should be filed to bugs.freedesktop.org (set product as "DRI", component as "hsakmt") I will package this release for Fedora 22,...

...ou need to include OpenCL library headers from libclc > (http://libclc.llvm.org/) to compile most OpenCL code. > > Here is an example command: > > clang -include /path/to/libclc/headers/clc.h -I /path/to/libclc/headers -Dcl_clang_storage_class_specifiers -target amdgcn--amdhsa -mcpu=carrizo $INPUT_FILE -o $OUTPUT_FILE Hi Tom, to piggy-pack on this question. To load this kernel in OpenCL, is it sufficient to just pass $OUTPUT_FILE to clCreateProgramWithBinary? Also, assuming this is enough. Is the code quality for recent AMD GPUs quality-wise on the level of what AMD's closed-s...

Hi LLVM, I would like to compile OpenCL kernel for a specific AMD GPU target. Is it possible with the current clang/LLVM? I started by using `clang -x cl` but it looks like at least some OpenCL specific headers are missing (e.g. uint2 is not recognized as a type). Any links to documentation / tutorials very welcome. Thanks. - Paweł -------------- next part -------------- An HTML attachment was

On Fri, May 19, 2017 at 4:01 PM Adam Nemet via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I will run it on Cyclone/AArch64 next week. > FYI, we're still waiting on these Adam... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170530/7cb390ca/attachment.html>

...ity will have access to particular hardware variants. > > > > On Tue, May 30, 2017 at 1:14 AM Flamedoge <code.kchoi at gmail.com> wrote: > > Thank you for running these. > > > > May I suggest testing on AVX2 capable hardware? That would be Intel > Haswell, AMD Carrizo and up. > > I'm not sure what "vectorizer-maximize-bandwidth" implies, but doubling > the vector lanes may help light up parallel regions. > > > > Kevin > > > > On Tue, May 30, 2017 at 12:58 AM, Chandler Carruth via llvm-dev < > llvm-dev at lists...

...e in the community will have access to particular hardware variants. On Tue, May 30, 2017 at 1:14 AM Flamedoge <code.kchoi at gmail.com<mailto:code.kchoi at gmail.com>> wrote: Thank you for running these. May I suggest testing on AVX2 capable hardware? That would be Intel Haswell, AMD Carrizo and up. I'm not sure what "vectorizer-maximize-bandwidth" implies, but doubling the vector lanes may help light up parallel regions. Kevin On Tue, May 30, 2017 at 12:58 AM, Chandler Carruth via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrot...

...if defined(__cplusplus) +extern "C" { +#endif + #define DRM_AMDGPU_GEM_CREATE 0x00 #define DRM_AMDGPU_GEM_MMAP 0x01 #define DRM_AMDGPU_CTX 0x02 @@ -642,4 +646,8 @@ struct drm_amdgpu_info_hw_ip { #define AMDGPU_FAMILY_VI 130 /* Iceland, Tonga */ #define AMDGPU_FAMILY_CZ 135 /* Carrizo, Stoney */ +#if defined(__cplusplus) +} +#endif + #endif -- 2.6.2

This is the initial release of the xf86-video-amdgpu driver. It was forked from the xf86-video-ati radeon driver and modified to support the amdgpu kernel driver via libdrm_amdgpu, and by extension the latest AMD GPU families Tonga, Carrizo, Iceland, Fiji and Stoney. Some functionality was removed because it's not relevant for the GPUs supported by the amdgpu kernel driver, but other than that the two drivers are more or less on par with respect to functionality and bug fixes. Thanks to everybody who contributed to this release!...

Hi all, As some of you may know there some subtle distinction between C and C++ structs, thus one should wrap/annotate them roughly like below. ... #if defined(__cplusplus) extern "C" { #endif struct foo { int bar; ... }; ... #if defined(__cplusplus) } #endif In order to work around the lack of these users can wrap the header inclusion in the same way. For example:

...oreign function call (arg 5)" (I have 116 covariates, I'm using the "cr" basis to speed things up, the binomial family and, where necessary, have set the required k to lower than the number of distinct values for a given covarate when less than the default) Thank you, Savrina scarrizo at it.usyd.edu.au School of Information Technologies Univeristy of Sydney