search for: mlink

...ments a tool using the CSI API, the tool writer's implemented hooks override the corresponding default implementations. 3) A runtime library that implements certain powerful features of CSI, including contiguous sets of ID's for hooks. We've been thinking about how CSI might work with -mlink-bitcode-file. >From our admittedly limited understanding of that feature, it seems that a design that uses -mlink-bitcode-file would still require something like the first and third components of the existing design. Additional complexity might be needed to get CSI to work with -mlink-bitcode-f...

...ter's implemented hooks override the corresponding default >> implementations. >> 3) A runtime library that implements certain powerful features of CSI, >> including contiguous sets of ID's for hooks. >> >> We've been thinking about how CSI might work with -mlink-bitcode-file. >> From our admittedly limited understanding of that feature, it seems that a >> design that uses -mlink-bitcode-file would still require something like the >> first and third components of the existing design. Additional complexity >> might be needed to get C...

Hi, > which works but it produces LLVM IR code for all OpenCL intrinsics > implemented by libclc along with the kernel I am interested in, is their a > possibility to avoid this ? and only produce the llvm code for the kernel > required ? Mark all functions apart from the kernel entry points with the internal attribute and then run global dead code elimination (it should remove most

Hi Folks, We've been experimenting with magic symlinks. The first patch referred to below is a straight port of the patch in the netbsd pr database: http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=1781 For FreeBSD, the patch against -stable is at: http://people.freebsd.org/~jwd/mlinks/freebsd-magic-patches The second patch applies o...

On Thu, Jun 16, 2016 at 3:27 PM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi TB, > > Thanks for you answer. > > On Jun 16, 2016, at 2:50 PM, TB Schardl <neboat at mit.edu> wrote: > > Hey Mehdi, > > Thank you for your comments. I've CC'd the CSI mailing list with your > comments and put my responses inline. Please let me

Hi, My goal is to use Clang/LLVM/libclc to compile an OpenCL kernel and eventually generate a PTX code. I already did this but I am not sure if the PTX code I am generating is correct (is the one that is supposed to be generated). For example, currently, In OpenCL : get_global_id(0) translates to In LLVM : %call = tail call i32 @get_global_id(i32 0) which translates to In PTX:

...-S" "-disable-free" "-main-file-name" " axpy.cu" "-mrelocation-model" "static" "-mthread-model" "posix" "-mdisable-fp-elim" "-fmath-errno" "-no-integrated-as" "-fcuda-is-device" "-mlink-cuda-bitcode" "/usr/local/cuda/nvvm/libdevice/libdevice.compute_35.10.bc" "-target-feature" "+ptx42" "-target-cpu" "sm_35" "-dwarf-column-info" "-debugger-tuning=gdb" "-resource-dir" "/usr/local/google/home/ji...

...in/clang-9" -cc1 -triple nvptx64-nvidia-cuda -aux-triple x86_64-unknown-linux-gnu -S -disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib...

...in/clang-9" -cc1 -triple nvptx64-nvidia-cuda -aux-triple x86_64-unknown-linux-gnu -S -disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib...

...in/clang-9" -cc1 -triple nvptx64-nvidia-cuda -aux-triple x86_64-unknown-linux-gnu -S -disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib...

...in/clang-9" -cc1 -triple nvptx64-nvidia-cuda -aux-triple x86_64-unknown-linux-gnu -S -disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib...

...e" "-main-file-name" " >> axpy.cu" "-mrelocation-model" "static" "-mthread-model" "posix" >> "-mdisable-fp-elim" "-fmath-errno" "-no-integrated-as" "-fcuda-is-device" >> "-mlink-cuda-bitcode" >> "/usr/local/cuda/nvvm/libdevice/libdevice.compute_35.10.bc" >> "-target-feature" "+ptx42" "-target-cpu" "sm_35" "-dwarf-column-info" >> "-debugger-tuning=gdb" "-resource-dir" >...

Hi Alexey, Thanks for the great work! The version I checked out works most of the time. But I do encounter crashes sometimes. I can't file a bug report on https://bugs.llvm.org/ because I don't have an account. I sent an email to bugs-admin at lists.llvm.org for an account already but I haven't heard back. Meanwhile, can you take a look at the issue? I'm attaching the bug report

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed