search for: llvm_trunk

...S -D_DEBUG -D_GLIBCXX_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/clang/lib/Frontend/Rewrite -I/sw/src/clang_llvm_dev/clang/lib/Frontend/Rewrite -I/sw/src/clang_llvm_dev/clang/include -Itools/clang/include -Iinclude -I/sw/src/clang_llvm_dev/llvm_trunk/include -fopt-info -pipe -Wall -Wextra -Ofast -DCLS=64 -fPIC -floop-nest-optimize --param simultaneous-prefetches=16 -fprefetch-loop-arrays -msse4.2 -mrecip=all -funroll-loops -fdelete-null-pointer-checks --param prefetch-latency=32 -ffast-math -ftree-vectorize -f...

rkotler at ubuntu-rkotler:~/llvm_trunk$ svn update svn: OPTIONS of 'https://rkotler at llvm.org/svn/llvm-project/llvm/trunk': could not connect to server (https://llvm.org)

I"m getting build errors I think from one of your patches O tjoml. You need to have a build area that builds with clang and does warnings as errors to avoid these issues on putback. here is my configure step for example: /home/rkotler/llvm_trunk/configure --enable-werror --prefix=/home/rkotler/ll vm/install CC=/home/rkotler/llvm_3_2/install/bin/clang CXX=/home/rkotler/llvm_3_ 2/install/bin/clang++ You should run debug and retail builds too because the warnings can become serious if there is something used in a DEBUG that is only refe...

Hello, The Clang Visual Studio solution was modified yesterday. A reference to the file clang.vdproj was added but the file does not appear to be in the repository. Was this file missed during commit? The file is expected to be in llvm_trunk\clang\ Thanks, Javier -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081106/87595906/attachment.html>

...kotler at mips.com>: > I"m getting build errors I think from one of your patches O tjoml. > > You need to have a build area that builds with clang and does warnings as > errors to avoid these issues on putback. > > here is my configure step for example: > /home/rkotler/llvm_trunk/configure --enable-werror > --prefix=/home/rkotler/ll > vm/install CC=/home/rkotler/llvm_3_2/install/bin/clang > CXX=/home/rkotler/llvm_3_ > 2/install/bin/clang++ > > > You should run debug and retail builds too because the warnings can become > serious if there is something...

...gt; I"m getting build errors I think from one of your patches O tjoml. >> >> You need to have a build area that builds with clang and does warnings as >> errors to avoid these issues on putback. >> >> here is my configure step for example: >> /home/rkotler/llvm_trunk/configure --enable-werror >> --prefix=/home/rkotler/ll >> vm/install CC=/home/rkotler/llvm_3_2/install/bin/clang >> CXX=/home/rkotler/llvm_3_ >> 2/install/bin/clang++ >> >> >> You should run debug and retail builds too because the warnings can become >&g...

...z, Javier E a écrit : > Hello, > > > > The Clang Visual Studio solution was modified yesterday. A reference to > the file clang.vdproj was added but the file does not appear to be in > the repository. Was this file missed during commit? The file is expected > to be in llvm_trunk\clang\ > The file should be in the clang repository, not the llvm one and be named clang.vcproj (maybe a typo). If you use only llvm, don't use the clang solution. Or you may want to try the new cmake build sytem. Cédric > > > Thanks, > > Javier > > > ----...

...ther it will be new language constructs, similar to prallel_for >> in Cilk Plus, or will it be pragma-based like in OpenMP or OpenACC? >> >> The design I mentioned above has an operable implementation fon NVIDIA >> target at the >> >> https://github.com/clang-omp/llvm_trunk >> https://github.com/clang-omp/clang_trunk >> >> with runtime implemented at >> >> https://github.com/clang-omp/libomptarget >> >> you're welcome to try it out, if you have an appropriate device. >> >> Regards, >> Sergos >> >...

...linking step. Cheers, Roel On 09/06/15 00:07, Samuel Antão wrote: > Hi Roel, Chris, > > This is a summary on how you can add support for a a different > offloading device on top of what we have in github for OpenMP: > > a) Download and install lvm (https://github.com/clang-omp/llvm_trunk), > and clang (https://github.com/clang-omp/clang_trunk) as usual > > b) install the official llvm OpenMP runtime library openmp.llvm.org > <http://openmp.llvm.org>. Clang will expect that to be present in your > library path in order to compile OpenMP code (even if you do not...

...offloading, data transfer, scheduling and so on? Whether it will be new language constructs, similar to prallel_for in Cilk Plus, or will it be pragma-based like in OpenMP or OpenACC? The design I mentioned above has an operable implementation fon NVIDIA target at the https://github.com/clang-omp/llvm_trunk https://github.com/clang-omp/clang_trunk with runtime implemented at https://github.com/clang-omp/libomptarget you're welcome to try it out, if you have an appropriate device. Regards, Sergos On Sat, Jun 6, 2015 at 2:24 PM, Christos Margiolas <chrmargiolas at gmail.com> wrote: > H...

Hi, Lang. 2014-09-19 0:39 GMT+06:00 Lang Hames <lhames at gmail.com>: > Hi Anton, > > I don't follow what you're asking? > > For (1): You can compile c++ files to .ll files with clang - it seems like > you've already worked that out. > > For (2): What do you mean "supported at the moment"? In the 3.5 release > MCJIT is known to be broken for

llvm[2]: Compiling DWARFDebugArangeSet.cpp for Debug+Asserts build llvm[2]: Compiling DWARFDebugAranges.cpp for Debug+Asserts build llvm[2]: Compiling DWARFDebugFrame.cpp for Debug+Asserts build /home/rkotler/llvm_trunk/lib/DebugInfo/DWARFDebugFrame.cpp:118:8: error: private field 'LinkedCIE' is not used [-Werror,-Wunused-private-field] CIE *LinkedCIE; ^ 1 error generated. make[2]: *** [/home/rkotler/ On 02/05/2013 08:24 PM, Matt Beaumont-Gay wrote: > On Tue, Feb 5, 2013 at 3:30 PM,...

Christos, We would be very interested in learning more about this. In my group, we (Prakalp Srivastava, Maria Kotsifakou and I) have been working on LLVM extensions to make it easier to target a wide range of accelerators in a heterogeneous mobile device, such as Qualcomm's Snapdragon and other APUs. Our approach has been to (a) add better abstractions of parallelism to the LLVM instruction