public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/106897] driver: support -gz=zstd Date: Sat, 10 Sep 2022 07:58:02 +0000 [thread overview] Message-ID: <bug-106897-4-GECwvDN0wc@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 #4 from Fangrui Song <i at maskray dot me> --- Yes, the change will be straightforward, basically the files touched by the pending https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597586.html ("[PATCH] Remove legacy -gz=zlib-gnu"). I sent it because I knew that we would need a new compression format, and some cleanup would make the logic more maintainable.
next prev parent reply other threads:[~2022-09-10 7:58 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 [this message] 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 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-GECwvDN0wc@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: linkBe 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).