From: "Marc Nieper-Wißkirchen" <marc.nieper@gmail.com>
To: Petter Tomner <tomner@kth.se>
Cc: "jit@gcc.gnu.org" <jit@gcc.gnu.org>
Subject: Re: gcc_jit_context_new_rvalue_from_XXX
Date: Mon, 13 Dec 2021 16:12:16 +0100 [thread overview]
Message-ID: <CAEYrNrTqruOX2ZNquu2-aNZ4OxOGXz6mmUr0X5d-hJLLUw013g@mail.gmail.com> (raw)
In-Reply-To: <96f548e7b908479f88b65bf5ddca9e31@kth.se>
Thanks for your quick and helpful response!
Getting this into the trunk would be great!
Am Mo., 13. Dez. 2021 um 15:54 Uhr schrieb Petter Tomner <tomner@kth.se>:
> Hi!
>
> I posted a patch addressing long long some time ago.
>
> https://gcc.gnu.org/pipermail/jit/2021q4/001375.html
>
> long long should cover all integral types on all platforms as you can
> pick the result type as you want, assuming unsigned long long never
> has more bits than long long :/
>
> Regards, Petter
>
>
>
> Från: Jit <jit-bounces+tomner=kth.se@gcc.gnu.org> för Marc
> Nieper-Wißkirchen via Jit <jit@gcc.gnu.org>
> Skickat: den 13 december 2021 15:18
> Till: jit@gcc.gnu.org
> Ämne: gcc_jit_context_new_rvalue_from_XXX
>
> Hi,
>
> we have
>
> gcc_jit_context_new_rvalue_from_int
>
> and
>
> gcc_jit_context_new_rvalue_from_long.
>
> What about
>
> gcc_jit_context_new_rvalue_from_long_long
>
> and other integral types?
>
> It could be emulated with initialized globals (and relying on the
> optimization pass), but only when the binary representation on the target
> is known, which it generally isn't unless the target is always the host.
>
> Thanks,
>
> Marc
>
next prev parent reply other threads:[~2021-12-13 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 14:18 gcc_jit_context_new_rvalue_from_XXX Marc Nieper-Wißkirchen
2021-12-13 14:54 ` SV: gcc_jit_context_new_rvalue_from_XXX Petter Tomner
2021-12-13 15:12 ` Marc Nieper-Wißkirchen [this message]
2022-04-15 9:22 ` gcc_jit_context_new_rvalue_from_XXX Marc Nieper-Wißkirchen
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=CAEYrNrTqruOX2ZNquu2-aNZ4OxOGXz6mmUr0X5d-hJLLUw013g@mail.gmail.com \
--to=marc.nieper@gmail.com \
--cc=jit@gcc.gnu.org \
--cc=tomner@kth.se \
/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).