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>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: ICE with -Wlogical-op [PR107755]
Date: Tue, 31 Jan 2023 17:48:05 -0500	[thread overview]
Message-ID: <cd44a1e7-ab00-fa73-a370-359f71615b7e@redhat.com> (raw)
In-Reply-To: <20230131204134.725217-1-polacek@redhat.com>

On 1/31/23 15:41, Marek Polacek wrote:
> Here we crash in the middle end because warn_logical_operator calls
> build_range_check which calls various fold_* functions and those
> don't work too well when we're still processing template trees.  For
> instance here we crash because we're converting a RECORD_TYPE to bool.
> At this point VIEW_CONVERT_EXPR<struct Foo>(b) hasn't yet been converted
> to Foo::operator bool (&b).
> 
> I was excited to fix this with instantiation_dependent_expression_p
> which can now be called from c-family/ as well, but the problem isn't
> that the expression is dependent.  So, p_t_d it is.
> 
> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?

OK.

> 	PR c++/107755
> 
> gcc/cp/ChangeLog:
> 
> 	* call.cc (build_new_op): Don't call warn_logical_operator when
> 	processing a template.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* g++.dg/warn/Wlogical-op-4.C: New test.
> ---
>   gcc/cp/call.cc                            |  2 +-
>   gcc/testsuite/g++.dg/warn/Wlogical-op-4.C | 23 +++++++++++++++++++++++
>   2 files changed, 24 insertions(+), 1 deletion(-)
>   create mode 100644 gcc/testsuite/g++.dg/warn/Wlogical-op-4.C
> 
> diff --git a/gcc/cp/call.cc b/gcc/cp/call.cc
> index 5715a7cd1de..f7c5d9da94b 100644
> --- a/gcc/cp/call.cc
> +++ b/gcc/cp/call.cc
> @@ -7335,7 +7335,7 @@ build_new_op (const op_location_t &loc, enum tree_code code, int flags,
>       case TRUTH_ORIF_EXPR:
>       case TRUTH_AND_EXPR:
>       case TRUTH_OR_EXPR:
> -      if (complain & tf_warning)
> +      if ((complain & tf_warning) && !processing_template_decl)
>   	warn_logical_operator (loc, code, boolean_type_node,
>   			       code_orig_arg1, arg1,
>   			       code_orig_arg2, arg2);
> diff --git a/gcc/testsuite/g++.dg/warn/Wlogical-op-4.C b/gcc/testsuite/g++.dg/warn/Wlogical-op-4.C
> new file mode 100644
> index 00000000000..745c9117a3d
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/warn/Wlogical-op-4.C
> @@ -0,0 +1,23 @@
> +// PR c++/107755
> +// { dg-do compile }
> +// { dg-options "-Wlogical-op" }
> +
> +struct Foo
> +{
> +  operator bool() const { return false; }
> +};
> +
> +bool a;
> +Foo b;
> +
> +template <typename ignored>
> +static bool Bar()
> +{
> +  return (true && (false ? a : b));
> +  return (false || (false ? a : b));
> +}
> +
> +bool Baz()
> +{
> +  return Bar<void>();
> +}
> 
> base-commit: b2ec2504af77b35e748067eeb846821d12a6b6b4


      reply	other threads:[~2023-01-31 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 20:41 Marek Polacek
2023-01-31 22:48 ` 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=cd44a1e7-ab00-fa73-a370-359f71615b7e@redhat.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).