From: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
To: jit@gcc.gnu.org
Subject: Global register variables
Date: Tue, 31 Aug 2021 08:39:35 +0200 [thread overview]
Message-ID: <CAEYrNrScQ0FUOJv1Dw3C+ar649cLnYHitdC65dNEnd27PUaimA@mail.gmail.com> (raw)
Does libgccjit support GCC's global register variables ([1])?
If not, could we expect them to be included? One major use case of
libgccjit seems to be JIT compilation of some virtual machine bytecode and
virtual machines usually need a number of global variables (like some
virtual stack pointer or heap pointer, etc.). It makes a lot of sense to
hold them in global (callee-saved) registers.
Marc
--
[1]
https://gcc.gnu.org/onlinedocs/gcc/Global-Register-Variables.html#Global-Register-Variables
next reply other threads:[~2021-08-31 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 6:39 Marc Nieper-Wißkirchen [this message]
2021-09-02 14:33 ` David Malcolm
2021-09-02 16:05 ` Sv: " Petter Tomner
2021-09-02 16:33 ` Marc Nieper-Wißkirchen
2021-09-02 16:44 ` Sv: " David Malcolm
2021-09-02 17:06 ` Sv: " Petter Tomner
2021-09-02 17:09 ` Marc Nieper-Wißkirchen
2021-12-07 9:07 ` 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=CAEYrNrScQ0FUOJv1Dw3C+ar649cLnYHitdC65dNEnd27PUaimA@mail.gmail.com \
--to=marc.nieper+gnu@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).