Open VinInn opened 4 hours ago
cms-bot internal usage
A new Issue was created by @VinInn.
@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here
indeed (added a little #warning in the local file)
[innocent@patatrack03 binary64]$ hipcc -O3 oneComplex_hip.cpp -fopenmp
In file included from <built-in>:1:
In file included from /cvmfs/cms.cern.ch/el8_amd64_gcc12/external/rocm/5.6.1-afadfea30394e14bf2becdbebd346035/llvm/lib/clang/16.0.0/include/__clang_hip_runtime_wrapper.h:125:
In file included from /cvmfs/cms.cern.ch/el8_amd64_gcc12/external/rocm/5.6.1-afadfea30394e14bf2becdbebd346035/llvm/lib/clang/16.0.0/include/cuda_wrappers/complex:82:
/opt/rh/gcc-toolset-12/root/usr/lib/gcc/x86_64-redhat-linux/12/../../../../include/c++/12/complex:39:2: warning: This is complex from local installation [-W#warnings]
#warning This is complex from local installation
@fwyzard FYI
@VinInn , we pass --gcc-toolchain=$(COMPILER_PATH)
to hipcc
(as hipcc uses llvm on backend) (https://github.com/cms-sw/cmsdist/blob/IB/CMSSW_14_2_X/master/scram-tools.file/tools/rocm/rocm.xml#L18 ) when used within cmssw. I think llvm 13 and earlier versions were able to pick gcc headers from COMPILER_PATH
env variable but with llvm 14 and above we had to explicitly set --gcc-toolchain
( https://github.com/cms-sw/cmsdist/pull/8201 ) . I had opened an issue about this https://github.com/llvm/llvm-project/issues/56343 .
I'm confused about the actual origin of the c++ headers for hipcc (I assumed to be our gcc distribution. Instead it seems to come from a local installation
I'm in
If I compile something with it
so it seems to take gcc header files from /opt/rh/gcc-toolset-12/root/usr/lib/gcc/x86_64-redhat-linux/12/../../../../include/c++/12/ which actually does exist