From: Vibhav Pant <vibhavp@gmail.com>
To: jit@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] libgccjit.h: Make the macro definition for testing gcc_jit_context_new_bitcast correctly available.
Date: Sat, 23 Jul 2022 13:31:15 +0530 [thread overview]
Message-ID: <8ce556135d6366aeb434794e7247e8ca806ea736.camel@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 403 bytes --]
The macro definition for LIBGCCJIT_HAVE_gcc-jit_context_new_bitcast
was earlier located in the documentation comment for
gcc_jit_context_new_bitcast, making it unavailable to code that
consumed libgccjit.h. This patch moves the definition out of the
comment, making it effective.
Thanks,
Vibhav
--
Vibhav Pant
vibhavp@gmail.com
GPG: 7ED1 D48C 513C A024 BE3A 785F E3FB 28CB 6AB5 9598
[-- Attachment #1.2: 0001-Uncomment-macro-definition-for-testing-gcc_jit_conte.patch --]
[-- Type: text/x-patch, Size: 1256 bytes --]
From 13f7b010962d57a9a133b657838727486e4241c9 Mon Sep 17 00:00:00 2001
From: Vibhav Pant <vibhavp@gmail.com>
Date: Sat, 23 Jul 2022 13:18:05 +0530
Subject: [[PATCH] libgccjit.h: Make the macro definition for testing gcc_jit_context_new_bitcast correctly available.]
Uncomment macro definition for testing gcc_jit_context_new_bitcast support
The macro definition for LIBGCCJIT_HAVE_gcc-jit_context_new_bitcast
was earlier located in the documentation comment for
gcc_jit_context_new_bitcast, making it unavailable to code that
consumed libgccjit.h. This commit moves the definition out of the
comment, making it effective.
---
gcc/jit/libgccjit.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/jit/libgccjit.h b/gcc/jit/libgccjit.h
index 062f06d691a..b3c389e93f6 100644
--- a/gcc/jit/libgccjit.h
+++ b/gcc/jit/libgccjit.h
@@ -1252,10 +1252,10 @@ gcc_jit_context_new_cast (gcc_jit_context *ctxt,
gcc_jit_rvalue *rvalue,
gcc_jit_type *type);
-/* Reinterpret a value as another type.
-
#define LIBGCCJIT_HAVE_gcc_jit_context_new_bitcast
+/* Reinterpret a value as another type.
+
The types must be of the same size.
This API entrypoint was added in LIBGCCJIT_ABI_21; you can test for its
--
2.37.1
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-07-23 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 8:01 Vibhav Pant [this message]
2022-07-25 23:18 ` David Malcolm
2022-07-30 13:48 ` Vibhav Pant
2022-08-09 15:39 ` David Malcolm
2022-08-09 23:09 ` David Malcolm
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=8ce556135d6366aeb434794e7247e8ca806ea736.camel@gmail.com \
--to=vibhavp@gmail.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).