diff options
| author | Thomas Schwinge <tschwinge@baylibre.com> | 2025-10-21 09:46:32 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@baylibre.com> | 2025-10-24 12:40:22 +0200 |
| commit | 04df8fa9e73e612f978fff35a97841703b872f6c (patch) | |
| tree | 58f74906fbc08cbe2b9bc576b90885bf1f9ff6e6 /gcc/testsuite/jit.dg/test-error-array-bounds.c | |
| parent | 5bfa8d3a3da73c8953001f98ba166561bf9e8a4b (diff) | |
| download | gcc-04df8fa9e73e612f978fff35a97841703b872f6c.zip gcc-04df8fa9e73e612f978fff35a97841703b872f6c.tar.gz gcc-04df8fa9e73e612f978fff35a97841703b872f6c.tar.bz2 | |
Simplify 'Makefile' dependencies for libatomic [PR81358]
I noticed that commit r16-4315-ge63cf4b130b86dd7dde1bf499d3d40faca10ea2e
"PR81358: Enable automatic linking of libatomic" had introduced a lot of
repeated 'Makefile' dependencies for libatomic, including some nonsensical
ones, like 'configure-stage1-target-libada: maybe-all-stage1-target-libatomic'
(libada isn't bootstrapped). That's because the code for generation of
dependencies had been put into inside an existing loop over 'target_modules'.
PR driver/81358
* Makefile.tpl: Move generation of dependencies for libatomic out
of loop over 'target_modules'.
* Makefile.in: Regenerate.
Diffstat (limited to 'gcc/testsuite/jit.dg/test-error-array-bounds.c')
0 files changed, 0 insertions, 0 deletions