Hi Andrew,
Andrew Stubbs wrote:
I just realized that I'm assuming that -march=gfx1100 object files
will link with -march=gfx11-generic libraries, and produce gfx1100
binaries. Is this not the case?
Currently not: lld checks that the ELF ISA and flags (xnack, sramecc, …)
are identical and, if not, it fails to link.
So, the recommended way to silence the warning would be to use the
generic arch explicitly?
Yes – or, in special cases, to reconfigure + build GCC to have the
specific ISA available.
I think the latter would be the case with gfx942 (MI300A/MI300X) vs.
gfx9-4-generic when being compiled by an HPC center.
But for normal users, just specifying the generic instead (or ignoring
the warning) would be the default choice.
* * *
I use locally --with-multilib-
list=gfx906,gfx908,gfx90a,gfx90c,gfx1030,gfx1036,gfx1100,gfx1103,gfx9-
generic,gfx11-generic (i.e. no gfx900 and no gfx10-3-generic + none
of the newly added ones.)
And when plying around for testing all the patches, it works rather
smoothly.
Except you have warnings...
... but I also know what happens.
We could also classify the warning under [-Wopenmp] or … and permit
-Werror=… and -Wno-… for it. (I actually do not know whether '-w' and/or
'-Werror' are honored or not, but I bet either not or only limited.)
Tobias
