From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org, jit@gcc.gnu.org
Subject: [committed] jit: implement BT_CONST_VOLATILE_PTR [PR 95306]
Date: Wed, 3 Jun 2020 11:16:50 -0400 [thread overview]
Message-ID: <20200603151650.17157-1-dmalcolm@redhat.com> (raw)
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as r11-877-g6d36cc21b69d952967a4df6653954f572a101796.
gcc/jit/ChangeLog:
PR jit/95306
* jit-builtins.c (builtins_manager::make_primitive_type):
Implement BT_CONST_VOLATILE_PTR.
gcc/testsuite/ChangeLog:
PR jit/95306
* jit.dg/test-pr95306-builtin-types.c (create_code): Add
test of getting __atomic_load.
---
gcc/jit/jit-builtins.c | 4 +++-
gcc/testsuite/jit.dg/test-pr95306-builtin-types.c | 1 +
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/gcc/jit/jit-builtins.c b/gcc/jit/jit-builtins.c
index 4842ff3ea96..56a79b4e249 100644
--- a/gcc/jit/jit-builtins.c
+++ b/gcc/jit/jit-builtins.c
@@ -513,7 +513,9 @@ builtins_manager::make_primitive_type (enum jit_builtin_type type_id)
case BT_VOLATILE_PTR:
return (m_ctxt->get_type (GCC_JIT_TYPE_VOID)->get_volatile ()
->get_pointer ());
- // case BT_CONST_VOLATILE_PTR:
+ case BT_CONST_VOLATILE_PTR:
+ return (m_ctxt->get_type (GCC_JIT_TYPE_VOID)->get_const ()
+ ->get_volatile ()->get_pointer ());
// case BT_PTRMODE:
case BT_INT_PTR:
return m_ctxt->get_type (GCC_JIT_TYPE_INT)->get_pointer ();
diff --git a/gcc/testsuite/jit.dg/test-pr95306-builtin-types.c b/gcc/testsuite/jit.dg/test-pr95306-builtin-types.c
index 6c3b087ab98..960163ed7d4 100644
--- a/gcc/testsuite/jit.dg/test-pr95306-builtin-types.c
+++ b/gcc/testsuite/jit.dg/test-pr95306-builtin-types.c
@@ -8,6 +8,7 @@ create_code (gcc_jit_context *ctxt, void *user_data)
#define CHECK_BUILTIN(NAME) \
CHECK_NON_NULL (gcc_jit_context_get_builtin_function (ctxt, NAME));
+ CHECK_BUILTIN ("__atomic_load");
CHECK_BUILTIN ("__builtin_memcpy");
CHECK_BUILTIN ("__builtin_sadd_overflow");
--
2.26.2
reply other threads:[~2020-06-03 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200603151650.17157-1-dmalcolm@redhat.com \
--to=dmalcolm@redhat.com \
--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).