[Bug lto/95224] -flto -save-temps uses very unusual name for resolution file, looks arbitrary

[aoliva at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95224

Alexandre Oliva  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Alexandre Oliva  ---
The changes to the handling of '%u' under -save-temps have probably fixed this.
 Previously, we'd use input_basename unconditionally.

[Bug lto/95224] -flto -save-temps uses very unusual name for resolution file, looks arbitrary

[aoliva at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95224

--- Comment #2 from Alexandre Oliva  ---
That's not expected, but it seems highly suspicious indeed.  I'll have a look.

[Bug lto/95224] -flto -save-temps uses very unusual name for resolution file, looks arbitrary

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95224

Richard Biener  changed:

   What|Removed |Added

 CC||aoliva at gcc dot gnu.org

--- Comment #1 from Richard Biener  ---
ISTR seeing dups about this.  We seem to be happy to pick anything remotely
resembling a linker output as basename (-lm here).

Alex, do your patches change anything here?