Hi Jakub, hello world Jakub Jelinek wrote:
On Wed, Apr 03, 2024 at 11:09:19AM +0200, Tobias Burnus wrote:@@ -3954,8 +3956,8 @@ on the GPU. To enable support for GCN3 Fiji devices (gfx803), GCC has to be configured with @option{--with-arch=@code{fiji}} or @option{--with-multilib-list=@code{fiji},...}. Note that support for Fiji [...] +devices has been removed in ROCm 4.0 and support in LLVM is deprecated and has +been removed in LLVM 18.Shouldn't we at configure time then detect the case where fiji can't be supported and either error if it is included explicitly in multilib list, or implicitly take it out from that list and arrange error to be emitted when using -march=fiji/gfx803 ?
I am not sure that it is really needed for the reasons given below. And while it would help some specific use (having LLVM 17 and wanting to use Fiji), it will also cause some confusion as GCC 14 will magically behave differently depending how build. Additionally: * I bet most use gcc/config.gcc which works in most cases just fine (LLVM >= 17; enabling all but Fiji) * Fiji itself is old – removed from recent ROCm and LLVM >= 18, which also implies that it is seen as not seeing a lot of use While there is no configure-time check, using Fiji with LLVM 18 will fail with a semi-clear compile-time error when doing the in-tree newlib build or the libgomp build. (This shows up by default as issue with LLVM 18 + GCC 12/13; see https://gcc.gnu.org/PR114419) Likewise, it will fail with LLVM < 15 when building gfx1100/gfx1103. * * * Note: The compiler itself is perfectly happy to handle fiji and gfx1100 itself, just the LLVM MC assembler doesn't support one [< 15] or the other [>=LLVM 18]. * * * For those tracking GCC or caring, the documentation at https://gcc.gnu.org/gcc-14/changes.html#amdgcn and https://gcc.gnu.org/install/specific.html#amdgcn-x-amdhsa provides some glory details. And it is also mentioned at https://gcc.gnu.org/wiki/Offloading Tobias
