aboutsummaryrefslogtreecommitdiff
path: root/libjava/gnu/java
diff options
context:
space:
mode:
authorJoseph Myers <josmyers@redhat.com>2026-01-26 16:49:29 +0000
committerJoseph Myers <josmyers@redhat.com>2026-01-26 16:49:29 +0000
commite373a57b07de9290e8e3f6913f4179404f0b886e (patch)
treefbe5d764fa249646afbf5d33d196dcc354f0c802 /libjava/gnu/java
parenta33091a696a468db80253e031b15dcf0cc6db521 (diff)
downloadgcc-e373a57b07de9290e8e3f6913f4179404f0b886e.zip
gcc-e373a57b07de9290e8e3f6913f4179404f0b886e.tar.gz
gcc-e373a57b07de9290e8e3f6913f4179404f0b886e.tar.bz2
testsuite: Make profopt-execute also copy profile data for dg-additional-sources
Most gcc.dg/tree-prof tests work correctly in environments where .gcda files from the first run need to be copied from the target, because there is existing code in profopt-execute to do so. A few tests using dg-additional-sources fail because that code only copies the .gcda file for the main test source file. Add similar code to copy it for any sources listed in dg-additional-sources as well. The use of additional_sources_used is consistent with what profopt-target-cleanup does. It turns out to require the added call to cleanup-after-saved-dg-test to avoid additional_sources_used leaking from one test into the next. Tested for x86_64-pc-linux-gnu to make sure native testing isn't broken, and with cross to aarch64-linux. * lib/profopt.exp (profopt-execute): Also copy profile data from target for additional sources. Call cleanup-after-saved-dg-test before normal return.
Diffstat (limited to 'libjava/gnu/java')
0 files changed, 0 insertions, 0 deletions