From: Vibhav Pant <vibhavp@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] comp.c: Use the newly added bitcast API for type coercion, when available. (feature/jit-improved-type-punning)
Date: Wed, 05 Oct 2022 14:51:46 +0530 [thread overview]
Message-ID: <b235c84e4939782e1fee7df648901214406375f0.camel@gmail.com> (raw)
In-Reply-To: <xjflepv8mca.fsf@ma.sdf.org>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
On Tue, 2022-10-04 at 18:39 +0000, Andrea Corallo wrote:
> Vibhav Pant <vibhavp@gmail.com> writes:
>
> > On Wed, 2022-09-28 at 12:37 +0000, Andrea Corallo wrote:
> > > thanks for the patch, please find some comments below.
> > Hi Andrea,
> >
> > Thanks for the feedback.
> >
> > >
> > > Could you clarify why we need this double cast in both cases
> > > here?
> > >
> >
> > gcc_jit_context_new_bitcast requires that the types being converted
> > between have the same layout and as such, doesn't allow converting
> > between an arbitrarily sized integer/boolean and a pointer. Casting
> > it
> > to a uintptr/void* is still necessary, to ensure that it can be
> > bitcast
> > into a void*/uintptr respectively.
>
> I see thanks, I'd like to have a comment recording this in the code.
>
Good idea, done.
> > >
> The patch is okay for me with the suggestions implemented. I assume
> you
> have write access, if is not the case just post the patch here and
> I'll
> install it.
>
Sure, I merged the branch last night. Thanks for the help.
Best,
Vibhav
--
Vibhav Pant
vibhavp@gmail.com
GPG: 7ED1 D48C 513C A024 BE3A 785F E3FB 28CB 6AB5 9598
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-05 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 18:15 [PATCH] comp.c: Use the newly added bitcast API for type coercion, when available. (feature/jit-improved-type-punning) Vibhav Pant
2022-09-27 18:18 ` Lars Ingebrigtsen
2022-09-28 12:39 ` Andrea Corallo
2022-09-28 12:37 ` Andrea Corallo
2022-10-02 17:27 ` Vibhav Pant
2022-10-04 18:39 ` Andrea Corallo
2022-10-05 9:21 ` Vibhav Pant [this message]
2022-10-05 10:42 ` Andrea Corallo
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b235c84e4939782e1fee7df648901214406375f0.camel@gmail.com \
--to=vibhavp@gmail.com \
--cc=akrl@sdf.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).