[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Question about how to handle HIP vs hipamd



Greetings,

Étienne Mollier, on 2022-05-14:
> After setting a few missing environment variables and installing
> missing components in the build environment, I end up with a
> bunch of the following errors:
> 
> 	In file included from /<<PKGBUILDDIR>>/hip/tests/src/deviceLib/hipMathFunctions.cpp:29:
> 	In file included from /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/include/hip/hip_runtime.h:54:
> 	In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/thread:44:
> 	In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/this_thread_sleep.h:38:
> 	In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/chrono:41:
> 	/usr/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/limits:316:33: error: function return value cannot have __fp16 type; did you forget * ?
> 	      static _GLIBCXX_CONSTEXPR _Tp
> 	                                ^

I could work around the issue by setting the environment
variable HIP_CLANG_HCC_COMPAT_MODE to 1.  I seem to go further
with building the test suite.  I don't know whether this is
ideal.  Now I'm stuck at the following:

	make  -f CMakeFiles/directed_tests.runtimeApi.memory.hipMemcpy2DFromArray.dir/build.make CMakeFiles/directed_tests.runtimeApi.memory.hipMemcpy2DFromArray.dir/depend
	/<<PKGBUILDDIR>>/hip/tests/src/runtimeApi/memory/hipManagedKeyword.cpp:11:1: error: unknown type name '__managed__'
	__managed__ float A[N];   // Accessible by ALL CPU and GPU functions !!!
	^
	make[5]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
	/<<PKGBUILDDIR>>/hip/tests/src/runtimeApi/memory/hipManagedKeyword.cpp:12:1: error: unknown type name '__managed__'
	__managed__ float B[N];
	^
	/<<PKGBUILDDIR>>/hip/tests/src/runtimeApi/memory/hipManagedKeyword.cpp:13:1: error: unknown type name '__managed__'
	__managed__  int  x = 0;
	^

The __managed__ definition looks supposed to occur within the
hip specific part of clang: __clang_hip_runtime_wrapper.h.  I'm
under the impression I'm doing something very wrong, but don't
know what it is.  Opinions?

Kind regards,
-- 
Étienne Mollier <emollier@emlwks999.eu>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.

Attachment: signature.asc
Description: PGP signature


Reply to: