On 28/11/2025 13:04, Tobias Burnus wrote:
Andrew Stubbs wrote:
On 27/11/2025 16:42, Tobias Burnus wrote:
This patch addresses the first one by adding the generic
architectures - with the plan to removed the specific ones
in GCC 17 (except for gfx908/gfx90a which do not have
a generic arch).
I'm in two minds whether to just go ahead and remove the older
architectures right now? I wish I knew what devices people are using
in the wild (or even *if* anyone is using it).
The question is also which ROCm they use – as generic requires
ROCm 6.4.0, released on April 11, 2025. Meanwhile, the latest
6.4 release is 6.4.3 and the lastest release is 7.1.1 (Nov 26, 2025).
Also, if we're changing the default multilib (which we will be,
because explicit gfx900 is to be discontinued), then we need to think
about what the new default should be. Selfish me would like gfx90a,
but maybe one of the generics makes more sense?
For generic ones: gfx9-generic and gfx10-3-generic are still somewhat
widely used; newer ones have gfx11-generic but the gfx12-generic share
is increasing. (I ignore the few MI300 / gfx9-4-generic users).
* * *
Maybe we should just switch to the final plan now?
The attached patches (gcc + wwwdocs) now do so.
OK for GCC-16 mainline?
Tobias
OK, let's do this one, except:
GCC 15 and ROCm 4.8.0 (released April/May 2025) support generic archs.
Thus, by moving to generic archs, the number of multilibs build by GCC
can be reduced - while the number of supported devices increases.
I think that should be "6.4.0".
OK, with that fixed.
Andrew
