diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2026-01-07 14:29:44 +0000 |
|---|---|---|
| committer | Jonathan Wakely <redi@gcc.gnu.org> | 2026-02-06 09:54:14 +0000 |
| commit | 5bec884b2e890ffb950f1a3ccf325d92c3bf8496 (patch) | |
| tree | 1fc3a9cf2ceeeefedb1ceead0d3dac26838c6639 /libjava/classpath/java | |
| parent | 786e316de5c25a3fddeaa2003f6efb64fb5ab4a9 (diff) | |
| download | gcc-5bec884b2e890ffb950f1a3ccf325d92c3bf8496.zip gcc-5bec884b2e890ffb950f1a3ccf325d92c3bf8496.tar.gz gcc-5bec884b2e890ffb950f1a3ccf325d92c3bf8496.tar.bz2 | |
libstdc++: Allow new-abi-baseline target to overwrite existing file
There doesn't seem to be much benefit to writing the symbols to
baseline_symbols.txt.new when an existing file is already present. It
just adds a manual step for maintainers to move the .txt.new file to
replace the .txt one. Overwriting the file directly allows you to use
git diff to see what changed immediately, and you can easly use git
commands to revert to the original file too.
libstdc++-v3/ChangeLog:
* testsuite/Makefile.am (new-abi-baseline): Overwrite existing
file instead of creating baseline_symbols.txt.new.
* testsuite/Makefile.in: Regenerate.
Diffstat (limited to 'libjava/classpath/java')
0 files changed, 0 insertions, 0 deletions