public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Antoni Boucher <bouanto@zoho.com>,
	gcc-patches@gcc.gnu.org, jit@gcc.gnu.org
Cc: Guillaume Gomez <guillaume1.gomez@gmail.com>
Subject: Re: [PATCH] libgccjit: Allow comparing vector types
Date: Tue, 13 Dec 2022 16:24:05 -0500	[thread overview]
Message-ID: <03070a2e198b1e4a9f85c99bf52ecea567796b32.camel@redhat.com> (raw)
In-Reply-To: <1aec893b44d81c5558db3c3b2ac8b63e8c456469.camel@zoho.com>

On Mon, 2022-12-12 at 21:31 -0500, Antoni Boucher via Jit wrote:
> Hi.
> This fixes bug 108078.
> Thanks for the review.

[...snip...]

> diff --git a/gcc/jit/jit-recording.h b/gcc/jit/jit-recording.h
> index 5d7c7177cc3..4ec0fff4843 100644
> --- a/gcc/jit/jit-recording.h
> +++ b/gcc/jit/jit-recording.h
> @@ -806,6 +806,15 @@ public:
>  
>    void replay_into (replayer *) final override;
>  
> +  virtual bool is_same_type_as (type *other)

This would be better with a "final override" (and without the
"virtual").

> +  {
> +    vector_type *other_vec_type = other->dyn_cast_vector_type ();
> +    if (other_vec_type == NULL)
> +      return false;
> +    return get_num_units () == other_vec_type->get_num_units ()
> +      && get_element_type () == other_vec_type->get_element_type ();
> +  }
> +

OK for active branches with that nit fixed (though for gcc 10 you'd
have to spell final and override as "FINAL" and "OVERRIDE" due to
needing to be buildable with a C++98 compiler; not sure if gcc 10's
libgccjit even has vector types though).

[...snip...]

Thanks for the patch

Dave


  reply	other threads:[~2022-12-13 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  2:31 Antoni Boucher
2022-12-13 21:24 ` David Malcolm [this message]
2022-12-13 21:27   ` Antoni Boucher
2022-12-13 21:45     ` David Malcolm

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=03070a2e198b1e4a9f85c99bf52ecea567796b32.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=bouanto@zoho.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=guillaume1.gomez@gmail.com \
    --cc=jit@gcc.gnu.org \
    /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).