public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] Fix ICE due to c_safe_arg_type_equiv_p not checking for error_mark node
Date: Mon, 16 Oct 2023 17:40:15 -0400	[thread overview]
Message-ID: <ZS2tvzaCEqb753bz@redhat.com> (raw)
In-Reply-To: <20231015011648.1608638-1-pinskia@gmail.com>

On Sat, Oct 14, 2023 at 06:16:47PM -0700, Andrew Pinski wrote:
> This is a simple error recovery issue when c_safe_arg_type_equiv_p
> was added in r8-5312-gc65e18d3331aa999. The issue is that after
> an error, an argument type (of a function type) might turn
> into an error mark node and c_safe_arg_type_equiv_p was not ready
> for that. So this just adds a check for error operand for its
> arguments before getting the main variant.
> 
> OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.

Please don't include this line in the commit message.
 
> 	PR c/101285
> 
> gcc/c/ChangeLog:
> 
> 	* c-typeck.cc (c_safe_arg_type_equiv_p): Return true for error
> 	operands early.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.dg/pr101285-1.c: New test.
> ---
>  gcc/c/c-typeck.cc                 |  3 +++
>  gcc/testsuite/gcc.dg/pr101285-1.c | 10 ++++++++++
>  2 files changed, 13 insertions(+)
>  create mode 100644 gcc/testsuite/gcc.dg/pr101285-1.c
> 
> diff --git a/gcc/c/c-typeck.cc b/gcc/c/c-typeck.cc
> index e55e887da14..6e044b4afbc 100644
> --- a/gcc/c/c-typeck.cc
> +++ b/gcc/c/c-typeck.cc
> @@ -5960,6 +5960,9 @@ handle_warn_cast_qual (location_t loc, tree type, tree otype)
>  static bool
>  c_safe_arg_type_equiv_p (tree t1, tree t2)
>  {
> +  if (error_operand_p (t1) || error_operand_p (t2))
> +    return true;

I thought it would be more natural to return false but that would result in:
cast between incompatible function types from 'void (*)(int *)' to 'void (*)(<type-error>)'
but we don't want that so pretending the cast is safe is probably better.

>    t1 = TYPE_MAIN_VARIANT (t1);
>    t2 = TYPE_MAIN_VARIANT (t2);
>  
> diff --git a/gcc/testsuite/gcc.dg/pr101285-1.c b/gcc/testsuite/gcc.dg/pr101285-1.c
> new file mode 100644
> index 00000000000..831e35f7662
> --- /dev/null
> +++ b/gcc/testsuite/gcc.dg/pr101285-1.c
> @@ -0,0 +1,10 @@

Let's put

/* PR c/101285 */

here.

> +/* { dg-do compile } */
> +/* { dg-options "-W -Wall" } */
> +const int b;
> +typedef void (*ft1)(int[b++]); /* { dg-error "read-only variable" } */
> +void bar(int * z);
> +void baz()
> +{
> +    (ft1) bar; /* { dg-warning "statement with no effect" } */
> +}
> +

Extra newline.

Thanks,
Marek


      parent reply	other threads:[~2023-10-16 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15  1:16 Andrew Pinski
2023-10-15  1:16 ` [PATCH 2/2] [c] Fix PR 101364: ICE after error due to diagnose_arglist_conflict not checking for error Andrew Pinski
2023-10-16 21:38   ` Joseph Myers
2023-10-16 21:38 ` [PATCH 1/2] Fix ICE due to c_safe_arg_type_equiv_p not checking for error_mark node Joseph Myers
2023-10-16 21:40 ` Marek Polacek [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=ZS2tvzaCEqb753bz@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).