public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to remove WITH_CLEANUP_EXPR handling
Date: Tue, 04 Jul 2017 02:03:00 -0000	[thread overview]
Message-ID: <CADzB+2k5MKtf+Md_x_Qu9WxGc7rwszJStiHYyAOJ-j=7Nk+kdQ@mail.gmail.com> (raw)
In-Reply-To: <20170703093533.GG23803@redhat.com>

Absolutely.

On Mon, Jul 3, 2017 at 5:35 AM, Marek Polacek <polacek@redhat.com> wrote:
> On Thu, Jun 29, 2017 at 05:44:25PM -0400, Jason Merrill wrote:
>> The C++ front end hasn't generated WITH_CLEANUP_EXPR in a very long
>> time (20+ years?), so there's no need to handle it.
>
> Heh.  Found another one; is this patch ok if it passes testing?
>
> 2017-07-03  Marek Polacek  <polacek@redhat.com>
>
>         * c-warn.c (warn_if_unused_value): Remove WITH_CLEANUP_EXPR handling.
>
> diff --git gcc/c-family/c-warn.c gcc/c-family/c-warn.c
> index 5d67395..b9378c2 100644
> --- gcc/c-family/c-warn.c
> +++ gcc/c-family/c-warn.c
> @@ -465,7 +465,6 @@ warn_if_unused_value (const_tree exp, location_t locus)
>      case TARGET_EXPR:
>      case CALL_EXPR:
>      case TRY_CATCH_EXPR:
> -    case WITH_CLEANUP_EXPR:
>      case EXIT_EXPR:
>      case VA_ARG_EXPR:
>        return false;
>
>         Marek

      reply	other threads:[~2017-07-04  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 21:44 Jason Merrill
2017-06-30 12:39 ` Nathan Sidwell
2017-07-03  9:35 ` Marek Polacek
2017-07-04  2:03   ` Jason Merrill [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='CADzB+2k5MKtf+Md_x_Qu9WxGc7rwszJStiHYyAOJ-j=7Nk+kdQ@mail.gmail.com' \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=polacek@redhat.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).