https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68512
Bug ID: 68512
Summary: Non-deterministic behavior from gcc
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: odell.wood at gmail dot com
Target Milestone: ---
I've been struggling with bugs in gcc that cause non-reproducible errors for a
while now, pretty much every time I try to build a project from source. The
latest error is coming up when I try to build cutorch.
Command which causes non-reproducible bug:
/usr/local/cuda-7.0/bin/nvcc
/home/thomas/documents/code/torch/extra/cutorch/lib/THC/THCTensorMathPointwise.cu
-c -o
/home/thomas/documents/code/torch/extra/cutorch/build/lib/THC/CMakeFiles/THC.dir//./THC_generated_THCTensorMathPointwise.cu.o
-ccbin /usr/bin/cc -m64 -DTHC_EXPORTS -Xcompiler
,\"-fPIC\",\"-O3\",\"-DNDEBUG\" -gencode arch=compute_52,code=sm_52 -gencode
arch=compute_50,code=sm_50 -DNVCC -I/usr/local/cuda-7.0/include
-I/home/thomas/documents/code/torch/install/include
-I/home/thomas/documents/code/torch/install/include/TH
-I/usr/local/cuda-7.0/include
-I/home/thomas/documents/code/torch/extra/cutorch/lib/THC/CUDA_SDK_ROOT_DIR-NOTFOUND/common/inc
-I/home/thomas/documents/code/torch/extra/cutorch/build/lib/THC
In file included from
tmpxft_00003a7f_00000000-7_THCTensorMathPointwise.compute_52.cudafe1.stub.c:1:0:
/tmp/tmpxft_00003a7f_00000000-7_THCTensorMathPointwise.compute_52.cudafe1.stub.c:
In function ‘void
__sti____cudaRegisterAll_69_tmpxft_00003a7f_00000000_10_THCTensorMathPointwise_compute_50_cpp1_ii_f2e6419b()’:
/tmp/tmpxft_00003a7f_00000000-7_THCTensorMathPointwise.compute_52.cudafe1.stub.c:4257:361:
internal compiler error: in schedule_block, at haifa-sched.c:6296
static void
__sti____cudaRegisterAll_69_tmpxft_00003a7f_00000000_10_THCTensorMathPointwise_compute_50_cpp1_ii_f2e6419b(void){__cudaRegisterBinary(__nv_cudaEntityRegisterCallback);}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
If I try it again, it works fine.
