search for: 4.8

Hi Justin, Thanks for your response! The clang & llvm I'm using was built from source. Below is the output of compiling with -v. Any suggestions would be appreciated! *clang version 3.9.0 (trunk 270145) (llvm/trunk 270133)* *Target: x86_64-unknown-linux-gnu* *Thread model: posix* *InstalledDir: /usr/local/bin* *Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8*

OK, I see the problem. You were right that we weren't picking up libdevice. CUDA 7.0 only ships with the following libdevice binaries (found /path/to/cuda/nvvm/libdevice): libdevice.compute_20.10.bc libdevice.compute_30.10.bc libdevice.compute_35.10.bc If you ask for sm_50 with cuda 7.0, clang can't find a matching libdevice binary, and it will apparently silently give up and try to

Hi, Yuanfeng. What version of clang are you using? CUDA is only known to work at tip of head, so you must build clang yourself from source. I suspect that's your problem, but if building from source doesn't fix it, please attach the output of compiling with -v. Regards, -Justin On Sun, Jul 31, 2016 at 9:24 PM, Chandler Carruth <chandlerc at google.com> wrote: > Directly

On Fri, Mar 4, 2016 at 5:50 PM, Yuanfeng Peng <yuanfeng.jack.peng at gmail.com> wrote: > Hi Jingyue, > > My name is Yuanfeng Peng, I'm a PhD student at UPenn. I'm sorry to bother > you, but I'm having trouble with gpucc in my project, and I would be really > grateful for your help! > > Currently we're trying to instrument CUDA code using LLVM 3.9, and

Dear R-SIG-Debians, I have difficulties installing packages from within R through install.packages(). R version is 3.2.0 and OS is Linux Mint 17.1. For most packages, a lot of error messages come up which seem to be related to compilation. Installing packages provided by the ubuntu distro through apt-get works just fine. I followed all directions given in CRAN's

hi to all FreeBSD user. i have a problem about updating from 4.8-RELEASED to 4.8-STABLE, here's exactly what i did: first: cvsup -g -L 2 stable-supfile, where my stable-supfile is located at /root. 2nd: cd /usr/src; make buildworld; make buildkernel KERNCONF=BUFDAEMON; make installkernel KERNCONF=BUFDAEMON 3rd: reboot; mergemaster -p; make installworld; mergemaster; reboot. after

Thanks Nirav, I can confirm that this works when I do the compile with llc, but then when linking to an executable with clang (patched with http://reviews.llvm.org/D20352 and compiler-rt patched with http://reviews.llvm.org/D21612) on Linux, I'm getting something different. Here's a sample of the transcript, and what I'm seeing: --->8 clang invocation 8<--- [16-06-23 3:33:42]

At the end of March, the RELENG_4_8 (sometimes called 4.8-SECURITY) branch will reach its designated End of Life and cease to be supported by the FreeBSD Security Team. Released in April 2003, FreeBSD 4.8 was the first release designated for "extended" two-year security support instead of the normal one-year support. Over this time, 27 security advisories have been issued which have

Hi, Consider below test case: 1 #include <unordered_map> 2 3 using key=const int; 4 struct Myhash { 5 Myhash() = default; 6 std::hash<int> hash_int_t; 7 inline size_t operator()(const key& x) const throw() { 8 return hash_int_t(x); 9 } 10 }; 11

Hello, I am very new to FreeBSD and just installed 4.8 release. I want to upgrade this to stable. I have printed some of the pages out for makeworld and CVSUP, I am wondering what the best method for doing the updates are, downloading the individual packages and installing or using the CVSUP to do this? Currently I used mostly Red Hat Linux but have wanted to give this a try for some time

Dear Stefan, I have no idea where the problem is, but I feel this strong urge to mention that install.packages("sem") works fine on Debian squeeze (g++ 4.4.5), wheezy (g++ 4.7.2) and jessie (g++ 4.9.2) using the R backport from CRAN... Kind regards, Johannes Am Donnerstag, 7. Mai 2015, 09:39:20 schrieb Dr. Stefan R?ttger: > Dear R-SIG-Debians, > > I have difficulties

Hi, I installed CentOS 4.8 (not CentOS 5) on VMware Fusion using an ISO file I downloaded. During the installation, it asked me to enter a user name and its password. I tried to enter root for the user name, but it would not let me do that. So I had to enter a non-root user name. So I did not have the root user name and password when the installation completed. I only had a non-privileged user

Hi. I was wanting an initial opinion from the Release Team, about the Xen packages. Currently they are in bad shape in stretch and I intend to fix them ASAP. The question is whether I should move to Xen 4.7, or Xen 4.8. Xen 4.8 is currently at RC2 and seems in pretty good shape. I think it's more probable than not that we'll have Xen 4.8.0 by the Debian freeze date, but this is by no

Peter suggested just writing out '.byte 0xeb, 0x09' and that allowed the jump instruction to bypass the relaxation, so that fixes my immediate problem. The question still stands though whether it should be possible to do through the instruction builder interface. Cheers On Wed, Jun 22, 2016 at 10:40 AM Dean Michael Berris <dberris at google.com> wrote: > Thanks Nirav, > >

This is my output. I don''t know what to do to make this work. I have installed other gems without any problems. Suggestions? debian:/home/kevin# gem source -a http://www.rubygems.org http://www.rubygems.org added to sources debian:/home/kevin# gem install merb -V GET 302 Found: http://gems.rubyforge.org/latest_specs.4.8.gz GET 304 Not Modified:

Hi are there somewhere pkgs with xen 4.7 or 4.8 for centos7? -- ---------- Greetz Christoph

Hello, I installed 4.8-RELEASE a few weeks ago, and since I let the effort sit stagnant for a while I decided to do the cvsup/buildworld/buildkernel/installkernel/installworld/mergemaster/MAKEDEV steps to get current. Went fine, rebooted, then noticed that just one CPU was recognized: FreeBSD 4.8-STABLE #0: Thu Jun 19 17:05:20 PDT 2003

Hmm. Odd. I just rebuilt from scratch and it seems to work with the test/CodeGen/X86/xray-attribute-instrumentation.ll test case outputing straight to obj: llc -filetype=obj -o ~/a.o -mtriple=x86_64-apple-macosx < test/CodeGen/X86/xray-attribute-instrumentation.ll What test case are you using? In any case, the issue appears to be that llvm doesn't realize that the target address is

Hello All, We have some machines running CentOS 4 Update 4 (4.4). We want to update these boxes to the stock CentOS 4 Update 8 (4.8). We have the 4.8 iso images. Is it possible to use up2date and have it use the 4.8 mounted iso images on a remote (install) server as the repository? The ISO's are accessible through http. These servers are remote with no CD/DVD option to upgrade that way. I have

On 19/10/16 16:54, Ian Jackson wrote: > Ian Jackson writes ("Xen in stretch - 4.7 or 4.8 ?"): >> Hi. I was wanting an initial opinion from the Release Team, about the >> Xen packages. Currently they are in bad shape in stretch and I intend >> to fix them ASAP. >> >> The question is whether I should move to Xen 4.7, or Xen 4.8. > > I just asked