-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Labels
Bug in other softwareCompiler, Virtual Machine, etc. bug affecting OpenBLASCompiler, Virtual Machine, etc. bug affecting OpenBLAS
Description
As reported in issues #2236 and #2237 version 0.3.7 has problems with PGI.
Now that I have access to PGI 19.10, which fixes the MMX instructions problems, I tried again to build 0.3.7 after applying changes in #2223 (#2240 is no longer needed due to fixes in 19.10). I have tried both the llvm and nollvm compilers. They both produce the same result.
Now, the compile fails with (for example):
pgcc -c -O2 -DMAX_STACK_ALLOC=2048 -mp -tp p7-64 -DF_INTERFACE_PGI -fPIC -DNO_AVX512 -DSMP_SERVER -DUSE_OPENMP -DNO_WARMUP -DMAX_CPU_NUMBER=80 -DMAX_PARALLEL_NUMBER=1 -DVERSION=\"0.3.7\" -DASMNAME=dtrsm_iun\
ucopy -DASMFNAME=dtrsm_iunucopy_ -DNAME=dtrsm_iunucopy_ -DCNAME=dtrsm_iunucopy -DCHAR_NAME=\"dtrsm_iunucopy_\" -DCHAR_CNAME=\"dtrsm_iunucopy\" -DNO_AFFINITY -I.. -DDOUBLE -UCOMPLEX -DDOUBLE -UCOMPLEX -UOU\
TER -ULOWER -DUNIT generic/trsm_uncopy_4.c -o dtrsm_iunucopy.o
<inline asm>:2:13: error: invalid operand for instruction
addq $128, %dl
^~~
<inline asm>:5:15: error: invalid base+index expression
vmulpd -128(%dl), %xmm0, %xmm4
The invalid base+index expression error was mentioned in the discussion in #2237 here.
Does anyone know if a solution to the invalid base+index expression error was ever found? Or if there were other modifications found that were needed to get a clean build with PGI 19.10?
Metadata
Metadata
Assignees
Labels
Bug in other softwareCompiler, Virtual Machine, etc. bug affecting OpenBLASCompiler, Virtual Machine, etc. bug affecting OpenBLAS