public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] Add linker_output as prefix for LTO temps (PR lto/86548).
Date: Thu, 26 Jul 2018 11:35:00 -0000	[thread overview]
Message-ID: <CAFiYyc2HOy2gtsH6__tNSqUc56i4sSWCLqw0uNWv6Y0+cNUOFg@mail.gmail.com> (raw)
In-Reply-To: <d314ea1c-5c59-fcd3-9034-2973be882b31@suse.cz>

On Thu, Jul 26, 2018 at 12:55 PM Martin Liška <mliska@suse.cz> wrote:
>
> Hi.
>
> As requested in the PR, now we produce prefixes for temp files in LTO:
>
> Example:
> $ gcc -flto main.o a.o --save-temps -o mybinary
>
> generates:
> $ ls /tmp/mybinary*
> /tmp/mybinary  /tmp/mybinary.ltrans0.o  /tmp/mybinary.ltrans0.s  /tmp/mybinary.ltrans.out

It will be /tmp/mybinary.abc421.ltrans0.o
/tmp/mybinary.abc421.ltrans1.o, etc., correct?

Otherwise there's the chance to trash user files which isn't good.

> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?

OK if the above is correct.

Thanks,
Richard.

> Martin
>
> gcc/ChangeLog:
>
> 2018-07-26  Martin Liska  <mliska@suse.cz>
>
>         PR lto/86548
>         * lto-wrapper.c: Add linker_output as prefix
>         for ltrans_output_file.
>
> include/ChangeLog:
>
> 2018-07-26  Martin Liska  <mliska@suse.cz>
>
>         PR lto/86548
>         * libiberty.h (make_temp_file_with_prefix): New function.
>
> libiberty/ChangeLog:
>
> 2018-07-26  Martin Liska  <mliska@suse.cz>
>
>         PR lto/86548
>         * make-temp-file.c (TEMP_FILE): Remove leading 'cc'.
>         (make_temp_file): Call make_temp_file_with_prefix with
>         first argument set to NULL.
>         (make_temp_file_with_prefix): Support also prefix.
> ---
>  gcc/lto-wrapper.c          | 14 +++++++++++++-
>  include/libiberty.h        |  5 +++++
>  libiberty/make-temp-file.c | 24 ++++++++++++++++++------
>  3 files changed, 36 insertions(+), 7 deletions(-)
>
>

  reply	other threads:[~2018-07-26 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 10:55 Martin Liška
2018-07-26 11:35 ` Richard Biener [this message]
2018-07-26 12:12   ` Martin Liška
2018-07-26 12:27     ` Richard Biener
2018-07-26 13:53       ` Martin Liška

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFiYyc2HOy2gtsH6__tNSqUc56i4sSWCLqw0uNWv6Y0+cNUOFg@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mliska@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).