search for: steckelmacher

...ere (related to the PLT) that produces sequences of instructions, but not the other targets. So, what would be the best way to change "JCC imm9" instructions to something else when a branch has to jump further than 256 instructions before or after the current one? Best regards, Denis Steckelmacher

...in [2] the list of my past projects. During the GSoC 2011, I had the chance to use the Clang libraries to compile C code, and the LLVM JIT to execute it (with instrumented stdlib functions). I have also played with the LLVM C bindings to generate code when I explored some parts of Mesa. Denis Steckelmacher [1] : http://llvm.org/OpenProjects.html#misc_new [2] : http://steckdenis.be/page-projects.html

...efficient way to natively implement functions, without needing to have a LLVM pass turning LLVM intrinsics to native function calls. Here is my personal point of view, and I hope a solution will be found not to have three or four different projects working on the same things. Best regards, Denis Steckelmacher.

...ry is currently in fact fairly small, including just > a little more then the implementation-dependent functions. We are > considering merging efforts with liblcl in that point. Please excuse me for getting that wrong. I think we should really stick our heads together (also including Denis Steckelmacher who implemented Clover) and somehow combine all our efforts. Otherwise, we will probably just all solve the same problems in parallel. Additionally, no user will gain anything if he has to decide between multiple, half-baked solutions. Best, Ralf >> Am 19.10.2011 17:38, schrieb Hal Fink...

On 02/25/2014 04:50 PM, John Criswell wrote: > > I think a more interesting idea would be to use LLVM to perform > instrumentation and then to use Valgrind to instrument third-party > libraries linked into the program. > > What I'm imagining is this: Let's say you instrument a program with > SAFECode or Asan to find memory safety errors. When you run the program >

...e discussed how GPGPU should be handled and we kind of agreed on what we should do. This can basically be summed up as using the LLVM IR for compute. This means we need to implement LLVM backends for our GPUs. See the Mesa_compilers.pdf attachment. The OpenCL frontend has been implemented by Denis Steckelmacher during the GSoC 2011 (https://steckdenis.wordpress.com/2011/08/23/the-gsoc-is-over/) that currently works on the CPU only. This implementation work can be done by a newcomer, it requires knowledge (or willing to get it) in compilers. Please contact Martin Peres(mupuf) to get started. We'll see...

...ver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: martin.peres at ensi-bourges.fr QAContact: xorg-team at lists.x.org Created an attachment (id=51215) --> (https://bugs.freedesktop.org/attachment.cgi?id=51215) Tom Stellard's presentation Denis Steckelmacher (https://steckdenis.wordpress.com/2011/08/23/the-gsoc-is-over/) has been working hard to get OpenCL working on the CPU. At the XDC2011, we discussed how GPGPU should be handled and we kind of agreed on what we should do. This can basically be summed up as using the LLVM IR for compute. This means...

...airly small, including just >> a little more then the implementation-dependent functions. We are >> considering merging efforts with liblcl in that point. > Please excuse me for getting that wrong. > > I think we should really stick our heads together (also including Denis > Steckelmacher who implemented Clover) and somehow combine all our efforts. > Otherwise, we will probably just all solve the same problems in > parallel. Additionally, no user will gain anything if he has to decide > between multiple, half-baked solutions. > > Best, > Ralf > > > >&gt...

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

...t projects. During the GSoC 2011, > I had the chance to use the Clang libraries to compile C code, and the > LLVM JIT to execute it (with instrumented stdlib functions). I have also > played with the LLVM C bindings to generate code when I explored some > parts of Mesa. > > Denis Steckelmacher > > [1] : http://llvm.org/OpenProjects.html#misc_new > [2] : http://steckdenis.be/page-projects.html === End of the first message === The idea of using LLVM backend in some dynamic binary translation (DBT) project has became popular recently. Unfortunately it does not prove to be good....

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