On May 21, 2020, Alexandre Oliva <ol...@adacore.com> wrote: > On May 19, 2020, Richard Biener <rguent...@suse.de> wrote:
>> Thanks again for doing this. May I also suggest to prepare a short >> entry for gcc-11/changes.html with these things (like "Output of >> auxiliary files changed. See https://gcc.gnu.org/ml/gcc-patches/... >> for details")? > How about, under Caveats: > * Naming and location of auxiliary and dump output files changed. If > you compile multiple input files in a single command, if you enable Link > Time Optimization, or if you use -dumpbase, -dumpdir, -save-temps=*, and > you expect any file other than the primary output file(s) to be created > as a side effect, watch out for improvements and a few surprises. See > https://gcc.gnu.org/ml/... Here's the patch I'm pushing to wwwdocs: gcc-11/changes: -dump* and -aux* revamp --- htdocs/gcc-11/changes.html | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index e88a628..2f00d1f 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -30,7 +30,15 @@ a work-in-progress.</p> <!-- .................................................................. --> <h2>Caveats</h2> <ul> - <li>...</li> + <li>Naming and location of auxiliary and dump output files changed. + If you compile multiple input files in a single command, if you + enable Link Time Optimization, or if you use -dumpbase, + -dumpdir, -save-temps=*, and you expect any file other than the + primary output file(s) to be created as a side effect, watch out + for improvements and a few surprises. + See <a href="https://gcc.gnu.org/pipermail/gcc-patches/2020-May/546494.html">the + patch</a>, particularly its textual description, for more + details about the changes.</li> </ul> -- Alexandre Oliva, freedom fighter he/him https://FSFLA.org/blogs/lxo/ Free Software Evangelist Stallman was right, but he's left :( GNU Toolchain Engineer Live long and free, and prosper ethically