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 driver/106897] driver: support -gz=zstd
Date: Thu, 29 Sep 2022 09:27:49 +0000	[thread overview]
Message-ID: <bug-106897-4-t3uC6MM12p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106897-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:b7723e135334df95597c8c744276b9de5a88214a

commit r13-2931-gb7723e135334df95597c8c744276b9de5a88214a
Author: Martin Liska <mliska@suse.cz>
Date:   Thu Sep 22 14:30:44 2022 +0200

    support -gz=zstd for both linker and assembler

            PR driver/106897

    gcc/ChangeLog:

            * common.opt: Add -gz=zstd value.
            * configure.ac: Detect --compress-debug-sections=zstd
            for both linker and assembler.
            * configure: Regenerate.
            * gcc.cc (LINK_COMPRESS_DEBUG_SPEC): Handle -gz=zstd.
            (ASM_COMPRESS_DEBUG_SPEC): Likewise.

  parent reply	other threads:[~2022-09-29  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10  0:28 [Bug driver/106897] New: " i at maskray dot me
2022-09-10  0:33 ` [Bug driver/106897] " pinskia at gcc dot gnu.org
2022-09-10  0:36 ` pinskia at gcc dot gnu.org
2022-09-10  0:40 ` pinskia at gcc dot gnu.org
2022-09-10  3:09 ` pinskia at gcc dot gnu.org
2022-09-10  7:58 ` i at maskray dot me
2022-09-12 20:01 ` marxin at gcc dot gnu.org
2022-09-22 12:55 ` marxin at gcc dot gnu.org
2022-09-29  9:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-29  9:28 ` marxin at gcc dot gnu.org
2022-11-28 22:40 ` pinskia 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-106897-4-t3uC6MM12p@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).