similar to: opencl ???

Hi, I am trying to get a general feel of how usable Wine64 is. I just built 1.3.13. To see how well it works, I ran 64-bit Putty. It works flawlessly. Now, I am trying to play around with different little programs. I took "notepad.exe" from a Windows 7 install (hoping it would be a reasonably simple program for a start). It crashed with: fixme:heap:HeapSetInformation (nil) 1 (nil)

Hi, this is a follow-up on my email from august (http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-August/042737.html). i have, finally, released my OpenCL backend and control-flow restructuring framework for LLVM (AST-Extractor, or short axtor). The framework restructures function CFGs such that they can be expressed entirely without GOTOs or switch/loop-trickery. Hence, making it possible to

Simon, Have you looked at the control flow structizer that we have in the Open Source AMDIL backend? > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Simon Moll > Sent: Monday, March 05, 2012 1:01 PM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] OpenCL backend for LLVM > > Hi, > > this

The person that wrote our structurizer agrees with your analysis. Too bad the licenses are incompatible, it would be nice to merge similar efforts. > -----Original Message----- > From: Simon Moll [mailto:simon.m.moll at googlemail.com] > Sent: Tuesday, March 06, 2012 2:49 AM > To: Villmow, Micah > Cc: llvmdev at cs.uiuc.edu > Subject: RE: [LLVMdev] OpenCL backend for LLVM >

Hi Micah, i just had a quick look at your structurizer. Here is what if found (correct me, if i am mistaken): * Our approaches for handling Loops with multiple exits are identical. ("Loop-Exit Enumeration") * Axtor implements Controlled-Node Splitting and can cope with irreducible control-flow. (http://cardit.et.tudelft.nl/MOVE/papers/cc96.ps) * Axtor translates switches to cascading

Hi, This is to announce the availability of libclc, an open source, BSD licensed implementation of the library requirements of the OpenCL C programming language, as specified by the OpenCL 1.1 Specification. libclc is intended to be used with Clang's OpenCL frontend. libclc website: http://www.pcc.me.uk/~peter/libclc/ libclc is designed to be portable and extensible. To this end, it

Do we have a list of these open-source LLVM-based OpenCL projects somewhere? Off the top of my head, we have: libclc: http://www.pcc.me.uk/~peter/libclc/ pocl: https://launchpad.net/pocl clover: http://cgit.freedesktop.org/~steckdenis/clover/ (I think that all of these have BSD- or MIT-style licenses). Are there any others? -Hal On Wed, 2011-10-19 at 14:47 +0100, Peter Collingbourne wrote:

Hello everyone I was wondering, what the correct way of using an AMDGPU generated kernel code for OpenCL was. I am trying to provide Polly's GPGPU Code generation with the ability to run on different GPU devices, such as AMD GPUs. For NVIDIA, I simply retrieve a pre-compiled PTX string from the NVPTX backend and pass that to OpenCL's 'clCreateProgramWithBinary' function. However,

Hi Ralf, > The project started as a use-case for our "Whole-Function Vectorization" > library, which allows to transform a function to compute the same as W > executions of the original code by using SIMD instructions (W = 4 for > SSE/AltiVec, 8 for AVX). Quite interesting. We were planning to add "vectorization" to our passes also, but if I understood the

Ralf, What version of the SDK were you using for your analysis? I don't see that in the slides/pdf. Thanks, Micah > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Ralf Karrenberg > Sent: Wednesday, October 19, 2011 2:13 PM > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] ANN: libclc (OpenCL C

Hi Micah, The numbers from the paper were measured with the ATI Stream SDK v2.1 (it's only mentioned in the references I think). The most recent measurements I have were done with the current v2.5. Best, Ralf Am 19.10.2011 23:43, schrieb Villmow, Micah: > Ralf, > What version of the SDK were you using for your analysis? I don't see that in the slides/pdf. > > Thanks, >

Well well, LLVM seems to be everywhere these days :) >From the OpenCL SDK release notes: NOTICE: Portions of the NVIDIA system software contain components licensed from third parties under the following terms: Clang & LLVM: Copyright (c) 2003-2008 University of Illinois at Urbana-Champaign. All rights reserved. Portions of LLVM's System library: Copyright (C)

Hi everybody, the compiler design lab at Saarland University (chair of Sebastian Hack) is also working on an LLVM-based OpenCL driver. The project started as a use-case for our "Whole-Function Vectorization" library, which allows to transform a function to compute the same as W executions of the original code by using SIMD instructions (W = 4 for SSE/AltiVec, 8 for AVX). The

> NVIDIA did not commit the CUDA patches, yet. But plans to? 2012/1/5 Liu <proljc at gmail.com>: > On Thu, Jan 5, 2012 at 11:39 PM, Xin Tong <xerox.time.tech at gmail.com> wrote: >> I do not know too much about clang, is opencl publicly supported in >> clang ? how about cuda ? > > Anton at ARM commited theOpenCL patches, already. > > NVIDIA did not

> From: Peter Collingbourne [mailto:peter at pcc.me.uk] > Sent: 20 December 2010 20:11 > As with __local variables, it may be that "kernelness" cannot be > represented in a standard form in LLVM. For example on a CPU a > kernel function may have an additional parameter which is a pointer to > __local memory space, which would not be necessary on GPUs. Then in >

I do not know too much about clang, is opencl publicly supported in clang ? how about cuda ? Thanks Xin

Awesome, is the development of this being tracked somewhere? And is there a way I can get involved? Timothy On Tue, Dec 16, 2008 at 11:52 AM, Zack Rusin <zack at tungstengraphics.com> wrote: > On Tuesday 16 December 2008 12:21:24 Timothy Baldridge wrote: >> There seems to be some interest these days in OpenCL. However for some >> projects, a issue they face to adopting

Hi Carlos, On 10/20/11 9:54 AM, Carlos Sánchez de La Lama wrote: >> The project started as a use-case for our "Whole-Function Vectorization" >> library, which allows to transform a function to compute the same as W >> executions of the original code by using SIMD instructions (W = 4 for >> SSE/AltiVec, 8 for AVX). > > Quite interesting. We were planning to

On Thu, Jan 5, 2012 at 11:39 PM, Xin Tong <xerox.time.tech at gmail.com> wrote: > I do not know too much about clang, is opencl publicly supported in > clang ? how about cuda ? Anton at ARM commited theOpenCL patches, already. NVIDIA did not commit the CUDA patches, yet. > > Thanks > > Xin > _______________________________________________ > LLVM Developers mailing

Hi guys, I am understanding OpenCL compilation flow on GPU in order to develop OpenCL runtime for a new hardware. I understood that OpenCL compiler is part of a vendor's runtime library which is the heart of OpenCL. Since OpenCL kernel is compiled at runtime, hence at high level its compilation takes place in two steps: i. source code is first converted to intermediate code. ii.