From: Petter Tomner <tomner@kth.se>
To: "jit@gcc.gnu.org" <jit@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH 0/2] jit: Add support for complex types
Date: Tue, 14 Sep 2021 23:30:31 +0000 [thread overview]
Message-ID: <38cabc705eaf4fe6b26e312b4c5a2cd9@kth.se> (raw)
Hi!
The following two patches adds support for complex types in libgccjit.
The complex types already are in the types enum, however they are not usable.
In the patch, to use complex types, the user need to call a option function enabling
support. In this way, there will be a linking error if someone tries to use complex types
and a too old libgccjit.so, instead of a cryptic out of range enum error message at runtime.
Since the types already are in the enum, I saw no better way that wouldn't be confusing.
Patch 1 is implementation and patch 2 is docs and testcases.
check-jit runs fine on x64 Debian.
Regards,
Petter
next reply other threads:[~2021-09-14 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 23:30 Petter Tomner [this message]
2021-09-14 23:37 ` [PATCH 1/2] " Petter Tomner
2021-09-20 9:38 ` SV: " Petter Tomner
2021-09-27 12:37 ` Petter Tomner
2021-09-14 23:40 ` [PATCH 2/2] " 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=38cabc705eaf4fe6b26e312b4c5a2cd9@kth.se \
--to=tomner@kth.se \
--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).