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: Complex types and loong constants
Date: Thu, 21 Oct 2021 13:02:54 +0000 [thread overview]
Message-ID: <ee0d5b236d50452587f36b6b2ba29f87@kth.se> (raw)
Hi,
These two patches fixes support for complex types and adds the possibility to make
long long, long double and complex long double constants.
Please see follow up mails.
Regards,
next reply other threads:[~2021-10-21 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 13:02 Petter Tomner [this message]
2021-10-21 13:07 ` [PATCH 1/2] " Petter Tomner
2021-10-21 13:13 ` [PATCH 2/2] " Petter Tomner
2023-11-20 22:02 [PATCH 0/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=ee0d5b236d50452587f36b6b2ba29f87@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).