https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108287
--- Comment #5 from Georg-Johann Lay ---
...ok, yes, building outside srcdir won't fix this one. But points 1) and 2)
still apply.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108287
--- Comment #4 from Georg-Johann Lay ---
Well, updating or creating some auto-generated files is intentional.
What's not supported as of GCC documentation is configure'ing in the source
tree:
https://gcc.gnu.org/install/configure.html
> First
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108287
--- Comment #3 from Nicolas Mattia ---
(In reply to Andrew Pinski from comment #1)
> The best fix is do something similar to aarch64 in config/aarch64/t-aarch64:
> $(srcdir)/config/aarch64/aarch64-tune.md: s-aarch64-tune-md; @true
> s-aarch64-tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108287
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108287
--- Comment #1 from Andrew Pinski ---
The best fix is do something similar to aarch64 in config/aarch64/t-aarch64:
$(srcdir)/config/aarch64/aarch64-tune.md: s-aarch64-tune-md; @true
s-aarch64-tune-md: $(srcdir)/config/aarch64/gentune.sh \