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: Fangrui Song <maskray@google.com>,
	Andrew Pinski <pinskia@gmail.com>, Fangrui Song <i@maskray.me>,
	 GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Remove legacy -gz=zlib-gnu
Date: Wed, 21 Sep 2022 11:35:50 +0200	[thread overview]
Message-ID: <CAFiYyc1Vtsg4zAruSo8ev9uNL2_ZuAKrgM7-5EHaD1Tn6zF9WA@mail.gmail.com> (raw)
In-Reply-To: <6cfedac0-06b5-47d9-e2f8-0cc5b8c19244@suse.cz>

On Wed, Sep 21, 2022 at 9:49 AM Martin Liška <mliska@suse.cz> wrote:
>
> On 9/21/22 09:36, Richard Biener wrote:
> > If it's all configure time what's the point in
> > "deprecating" it?
>
> Note it's one of our options -gz where 'zlib-gnu' is one of the possible option values.

I see.  Not sure if deprecating is really necessary, you need to keep
recognizing
zlib-gnu as no-op anyway.  So I'd just go ahead and remove support for it.

> Martin

  reply	other threads:[~2022-09-21  9:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01  6:57 Fangrui Song
2022-07-01  7:03 ` Andrew Pinski
2022-07-01  7:20   ` Fangrui Song
2022-09-20 12:55     ` Martin Liška
2022-09-21  7:36       ` Richard Biener
2022-09-21  7:45         ` Fangrui Song
2022-09-21  7:49         ` Martin Liška
2022-09-21  9:35           ` Richard Biener [this message]
2022-09-22 11:10             ` [PATCH] remove -gz=zlib-gnu option value Martin Liška
2022-09-22 12:26               ` [PATCH v2] " Martin Liška
2022-09-22 12:35                 ` Richard Biener
2022-09-22 12:51                   ` [PATCH] support -gz=zstd for both linker and assembler Martin Liška
2022-09-27 13:54                     ` Martin Liška
2022-09-28 19:21                       ` Richard Biener

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=CAFiYyc1Vtsg4zAruSo8ev9uNL2_ZuAKrgM7-5EHaD1Tn6zF9WA@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@maskray.me \
    --cc=maskray@google.com \
    --cc=mliska@suse.cz \
    --cc=pinskia@gmail.com \
    /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).