On 22.03.2023 15:13, Jan Beulich wrote: > On 20.03.2023 16:28, Anthony PERARD wrote: >> This simple comment allows to detect when $(CC) changes version. >> Kconfig will be rerun in this case. (Rerun is forced by >> include/config/auto.conf.cmd which detects changes of CC_VERSION_TEXT >> value). >> >> Signed-off-by: Anthony PERARD <anthony.per...@citrix.com> >> --- >> >> Technically, it was acked by Andrew: >> >> https://lore.kernel.org/xen-devel/20200326135621.687685-1-anthony.per...@citrix.com/t/#ma1171775b9938bcdffc80b2fcb8d2a883cd3e32a > > And technically - comment visible under the same link - this still > isn't what we would need to address one of the arguments around not > storing tool chain capabilities in .config: The version string may > not change, but an update may still have brought a new option the > compiler understands (or a downgrade may have taken away one). In > fact this change is working against the proposed direction of not > making .config contents dependent upon tool chain properties. But > of course that proposal wasn't adopted yet, so for the time being > this still looks to be an improvement.
Coming back to this, seeing that there's unlikely to be any better approach any time soon, can we perhaps get this in then, ideally with $(LD) and the assembler backing the compiler (we don't use $(AS) anywhere, so we'd need to use e.g. "$$($(CC) -print-prog-name as) --version") also checked? Jan