public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-8674] libgccjit.h: Uncomment macro definition for testing gcc_jit_context_new_bitcast support
Date: Tue,  9 Aug 2022 23:08:47 +0000 (GMT)	[thread overview]
Message-ID: <20220809230847.D4AFF3858401@sourceware.org> (raw)

https://gcc.gnu.org/g:92f2582f3ec7b833a5f6b70ef05af4c7e511b860

commit r12-8674-g92f2582f3ec7b833a5f6b70ef05af4c7e511b860
Author: Vibhav Pant <vibhavp@gmail.com>
Date:   Tue Aug 9 19:06:43 2022 -0400

    libgccjit.h: Uncomment macro definition for testing gcc_jit_context_new_bitcast support
    
    (cherry-picked from r13-2004-g9385cd9c74cf66)
    
    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/ChangeLog:
            * libgccjit.h (LIBGCCJIT_HAVE_gcc_jit_context_new_bitcast): Move
            definition out of comment.
    
    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

Diff:
---
 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


                 reply	other threads:[~2022-08-09 23:08 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=20220809230847.D4AFF3858401@sourceware.org \
    --to=dmalcolm@gcc.gnu.org \
    --cc=gcc-cvs@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).