Bug#906753: Acknowledgement (GCC's -O2 optimization breaks floating point precision or something else)

This is the minimal code for repro #906753: OK with -O0, FAIL with -O2 on i386, ppc64el, ... masssq1 and masssq2 are computed from the same vector [1.1, 2.2, 3.3, 4.4], but the results are different! == #include #include // for swap #

Bug#906753: GCC's -O2 optimization breaks floating point precision or something else

Package: g++-8 Version: 8.2.0-4 Severity: serious Justification: -O2 results in different double precision number result. Affects: 906708 This bug is found in package src:hepmc, which currently FTBFS on i386, arm64, ppc64el and s390x. https://buildd.debian.org/status/package.php?p=hepmc - arm64:

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

>> That means, the "build your whole application with clang-3.8" >> advise is temporary and specific to CUDA 8.0. Before uploading >> CUDA 9.0 to unstable/experimental, we can change the default >> compiler back to GCC. And backporting CUDA 9.0 to stretch >> will eliminate the compiler trouble. > >

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

@doko GCC-5 may be removed from unstable when CUDA 9.0 is uploaded. See below. (Maybe doko is already in some of these lists.) > The problem is the move of some parts of the toolchain to pie by > default, without updating the whole toolchain. Whenever not using only > gcc for building object files

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

Hi, > This was documented in NEWS.Debian.gz. Having to use "--compiler-options > -fPIC" was however not documented in NEW.Debian.gz, at least that should > be done. > > Ok, but that's still something difficult to the user to work out, while > it is needed for basically any use of nvcc. Currently N

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

Hi Samuel, I'm not sure whether this bug should be marked as serious. Since your test cases are mixing the default cc (GCC-6) and clang-3.8 together. I reproduced the failure you reported, but there is a simpler solution to the issue as shown below. test$ CC=clang-3.8 make clang-3.8-c -o tes

Bug#850777: [gcc-6] internal compiler error on ppc64el (may be bug)

Package: gcc-6 Version: 6.3.0-2 Severity: normal Hi, GCC-6 failed when buildd is building torch7 package for ppc64el architecture. The buiild log can be found here: https://buildd.debian.org/status/fetch.php?pkg=lua-torch-torch7&arch=ppc64el&ver=0~20170106-gf624ae9-1&stamp=1483980176 Currently