From: David Malcolm <dmalcolm@redhat.com>
To: Antoni Boucher <bouanto@zoho.com>,
"jit@gcc.gnu.org" <jit@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libgccjit: Implement sizeof operator
Date: Wed, 10 Jan 2024 18:36:08 -0500 [thread overview]
Message-ID: <6c330fa1220dde767cacd055a644788cebe4ca83.camel@redhat.com> (raw)
In-Reply-To: <f2b03b3e5cebbe6a6f89021d02395dc454946bd7.camel@zoho.com>
On Wed, 2024-01-10 at 17:38 -0500, Antoni Boucher wrote:
> On Tue, 2024-01-09 at 11:33 -0500, David Malcolm wrote:
> > On Fri, 2023-12-22 at 10:25 -0500, Antoni Boucher wrote:
> > > Hi.
> > > This patch adds the support of the sizeof operator.
> > > I was wondering if this new API entrypoint should take a location
> > > as
> > > a
> > > parameter. What do you think?
> >
> > I'd prefer it if it did (even if it's currently ignored
> > internally),
> > but it's not a big deal.
>
> The reason it doesn't have a location is because it directly produces
> a
> constant, rather like gcc_jit_context_new_rvalue_from_int, which
> doesn't have a location either.
> So, I wanted to confirm that you think it's needed to have a
> location.
Fair enough; it's not needed.
>
> Also, I realized I misnamed memento_of_new_sizeof and will rename it
> to
> memento_of_sizeof.
Ah, ok. Fixing that is preapproved, though make sure it still builds
and test it a little before pushing!
Please also doublecheck the ABI version numbers, since they inevitably
tend to get out of sync on branches.
Dave
>
> >
> > > Thanks for the review.
> >
> > The patch is OK as-is.
> >
> > Thanks
> > Dave
> >
>
prev parent reply other threads:[~2024-01-10 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 15:25 Antoni Boucher
2024-01-09 16:33 ` David Malcolm
2024-01-10 22:38 ` Antoni Boucher
2024-01-10 23:36 ` David Malcolm [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=6c330fa1220dde767cacd055a644788cebe4ca83.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=bouanto@zoho.com \
--cc=gcc-patches@gcc.gnu.org \
--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).