public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/110710] LTO linker on Windows creates an invalid Makefile
Date: Thu, 02 May 2024 10:42:55 +0000	[thread overview]
Message-ID: <bug-110710-4-oKoPW28NOt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110710-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:985b5a90f70c7376c771317c6c8c3bc5ef05e227

commit r15-107-g985b5a90f70c7376c771317c6c8c3bc5ef05e227
Author: Peter Damianov <peter0x44@disroot.org>
Date:   Sun Apr 28 16:16:11 2024 -0700

    Driver: Add new -truncate option

    This commit adds a new option to the driver that truncates one file after
    linking.

    Tested likeso:

    $ gcc hello.c -c
    $ du -h hello.o
    4.0K  hello.o
    $ gcc hello.o -truncate hello.o
    $ ./a.out
    Hello world
    $ du -h hello.o
    $ 0   hello.o

    $ gcc hello.o -truncate
    gcc: error: missing filename after '-truncate'

    The motivation for adding this is PR110710. It is used by lto-wrapper to
    truncate files in a shell-independent manner.

    Signed-off-by: Peter Damianov <peter0x44@disroot.org>

            PR lto/110710
            * common.opt (truncate): New internal option.
            * gcc.cc (totruncate_file): New global.
            (driver_handle_option): Handle -truncate <file>.
            (driver::final_actions): Truncate the file indicated.

  parent reply	other threads:[~2024-05-02 10:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  6:14 [Bug lto/110710] New: " cz.finn.cz at gmail dot com
2023-07-18  6:18 ` [Bug lto/110710] " pinskia at gcc dot gnu.org
2023-07-18  6:22 ` pinskia at gcc dot gnu.org
2023-07-18  6:34 ` cz.finn.cz at gmail dot com
2023-07-18  6:39 ` pinskia at gcc dot gnu.org
2023-07-18  9:13 ` cz.finn.cz at gmail dot com
2024-02-13  2:16 ` amy at amyspark dot me
2024-03-14 16:13 ` peter0x44 at disroot dot org
2024-03-14 16:15 ` peter0x44 at disroot dot org
2024-03-14 16:15 ` peter0x44 at disroot dot org
2024-03-14 16:25 ` peter0x44 at disroot dot org
2024-03-15 14:49 ` peter0x44 at disroot dot org
2024-03-26 20:37 ` peter0x44 at disroot dot org
2024-03-26 22:45 ` peter0x44 at disroot dot org
2024-03-29 11:11 ` egallager at gcc dot gnu.org
2024-05-02 10:42 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-02 10:43 ` cvs-commit at gcc dot gnu.org
2024-05-02 10:43 ` rguenth at gcc dot gnu.org

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=bug-110710-4-oKoPW28NOt@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).