public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [PATCH (pushed)] clang warning: warning: private field 'm_gc' is not used [-Wunused-private-field]
Date: Wed, 3 May 2023 13:30:29 +0200	[thread overview]
Message-ID: <CAGm3qMVr1aiVH1f=5doeZ5PECYH1NL8cbPrA6EXak=gPbAmBfQ@mail.gmail.com> (raw)
In-Reply-To: <e14c76dc-af6a-78f7-4ae8-99f9b2c1a4c5@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

Thanks.

On Wed, May 3, 2023, 11:17 Martin Liška <mliska@suse.cz> wrote:

> Pushed to master as obvious.
>
> Martin
>
>         PR tree-optimization/109693
>
> gcc/ChangeLog:
>
>         * value-range-storage.cc (vrange_allocator::vrange_allocator):
>         Remove unused field.
>         * value-range-storage.h: Likewise.
> ---
>  gcc/value-range-storage.cc | 1 -
>  gcc/value-range-storage.h  | 1 -
>  2 files changed, 2 deletions(-)
>
> diff --git a/gcc/value-range-storage.cc b/gcc/value-range-storage.cc
> index 7d2de5e8384..14bec500dbc 100644
> --- a/gcc/value-range-storage.cc
> +++ b/gcc/value-range-storage.cc
> @@ -80,7 +80,6 @@ public:
>  };
>
>  vrange_allocator::vrange_allocator (bool gc)
> -  : m_gc (gc)
>  {
>    if (gc)
>      m_alloc = new vrange_ggc_alloc;
> diff --git a/gcc/value-range-storage.h b/gcc/value-range-storage.h
> index 4ec0da73059..a90b64b2bf0 100644
> --- a/gcc/value-range-storage.h
> +++ b/gcc/value-range-storage.h
> @@ -38,7 +38,6 @@ public:
>  private:
>    DISABLE_COPY_AND_ASSIGN (vrange_allocator);
>    class vrange_internal_alloc *m_alloc;
> -  bool m_gc;
>  };
>
>  // Efficient memory storage for a vrange.
> --
> 2.40.1
>
>

      reply	other threads:[~2023-05-03 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  9:17 Martin Liška
2023-05-03 11:30 ` Aldy Hernandez [this message]

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='CAGm3qMVr1aiVH1f=5doeZ5PECYH1NL8cbPrA6EXak=gPbAmBfQ@mail.gmail.com' \
    --to=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).