On May 25, 2026, Rainer Orth <[email protected]> wrote: > gcc: > * et-gather.awk, gen-et-static.awk: New scripts. > * Makefile.in (native): Depend on testsuite/et-static.exp. > (clean): Remove etlist. > (distclean): Remove et-static.exp. > (site.exp): Depend on testsuite/et-static.exp. > (testsuite/et-static.exp): New target.
> * doc/sourcebuild.texi (Effective-Target Keywords): Document > et-static.def. > (Effective-Target Keywords, Other attributes): Document > ld_at_file. > testsuite: > * lib/et-static.def: New file. > * lib/target-supports.exp: Load et-static.exp. > * gcc.misc-tests/outputs.exp: Use ld_at_file effective target > instead of gld. > Update comment. > contrib: > * test_installed (--with-auto-host-h): New option. > (--with-objc): Likewise. > (auto_host_h): Default to /dev/null. > Generate et-static.def. These changes look reasonable to me, thanks! I'm a little concerned about retaining the ability to preserve full-featured install testing without unnecessary effort for those who don't use test_installed specifically, or when no traces of the build tree have remained. One could presumably arrange to install or otherwise preserve auto-host.h, but wouldn't it make more sense to install the (presumably tiny) et-static.exp, and arrange for target-supports.exp to locate it and load it by running the compiler under test with -print-file-name=et-static.exp or somesuch, so that it is found both in the build tree and install tree testing? -- Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/ Free Software Activist FSFLA co-founder GNU Toolchain Engineer Learn the truth about Richard Stallman at https://stallmansupport.org/
