From: Basile Starynkevitch <basile@starynkevitch.net>
To: Petter Tomner <tomner@kth.se>
Cc: jit@gcc.gnu.org
Subject: Re: [RFC] Setting data segment and loong constants - WIP
Date: Wed, 6 Oct 2021 10:40:34 +0200 [thread overview]
Message-ID: <479456a4-997e-df56-302c-6d58e8090aff@starynkevitch.net> (raw)
In-Reply-To: <626c20889db34821ae574cae072b26c0@kth.se>
On 10/6/21 10:23 AM, Petter Tomner via Jit wrote:
> Hi,
>
> I have two patches I am working with and I wanted to share the concept
> if anyone has feedback. Both are dependent on my patch pending review
> on complex types:
> https://gcc.gnu.org/pipermail/jit/2021q3/001365.html
>
> So essentially it is one patch with:
>
> gcc_jit_context_new_rvalue_from_long_long (...)
> gcc_jit_context_new_rvalue_from_long_double (...)
> gcc_jit_context_new_rvalue_from_complex_long_double (...)
>
> Those do what it seems. long_long is for making 64bit constants on
> 32bit machines without silly workarounds.
>
>
> And one patch adding support for setting initial values of global
> variables:
>
> gcc_jit_lvalue *
> gcc_jit_global_set_initializer_rvalue (gcc_jit_lvalue *global,
> gcc_jit_rvalue *init_value);
>
> gcc_jit_rvalue *
> gcc_jit_context_new_constructor (gcc_jit_context *ctxt,
> gcc_jit_location *loc,
> gcc_jit_type *type,
> int arr_length,
> gcc_jit_field **fields,
> gcc_jit_rvalue **values);
I hope this patch would be approved.
(and we are considering perhaps using libgccjit in theRefPerSys project,
see http://refpersys.org/ for details)
Thanks
--
Basile Starynkevitch <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
next prev parent reply other threads:[~2021-10-06 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 8:23 Petter Tomner
2021-10-06 8:40 ` Basile Starynkevitch [this message]
2021-10-21 13:27 ` SV: " Petter Tomner
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=479456a4-997e-df56-302c-6d58e8090aff@starynkevitch.net \
--to=basile@starynkevitch.net \
--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).