https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
Martin Liška changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
--- Comment #8 from Martin Liška ---
Author: marxin
Date: Thu Jul 26 12:13:14 2018
New Revision: 262999
URL: https://gcc.gnu.org/viewcvs?rev=262999=gcc=rev
Log:
Add linker_output as prefix for LTO temps (PR lto/86548).
2018-07-26 Martin Liska
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
--- Comment #7 from Martin Liška ---
Patch was sent to mailing list:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01612.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
--- Comment #6 from Jonny Grant ---
(In reply to Richard Biener from comment #3)
> (In reply to Jonny Grant from comment #0)
> > It's pretty hard to work out which file this o file comes from. Could it
> > include the first file name in the tmp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
--- Comment #5 from Richard Biener ---
(In reply to Richard Biener from comment #3)
> (In reply to Jonny Grant from comment #0)
> > It's pretty hard to work out which file this o file comes from. Could it
> > include the first file name in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
--- Comment #4 from Jonny Grant ---
(In reply to Martin Liška from comment #2)
> I can implement that.
Great! Happy to pay bounty of $100 to you or GNU.
Could I ask for as short as possible tmp file name so output not too long. eg
could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
--- Comment #3 from Richard Biener ---
(In reply to Jonny Grant from comment #0)
> It's pretty hard to work out which file this o file comes from. Could it
> include the first file name in the tmp path to make it clearer where it came
> from?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
Martin Liška changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86548
Richard Biener changed:
What|Removed |Added
Keywords||lto
Status|UNCONFIRMED
