From: David Malcolm <dmalcolm@redhat.com>
To: vibhavp@gmail.com, jit@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgccjit.h: Make the macro definition for testing gcc_jit_context_new_bitcast correctly available.
Date: Mon, 25 Jul 2022 19:18:53 -0400 [thread overview]
Message-ID: <56d23606ae0212b3077bd617797ab14c465c6cc1.camel@redhat.com> (raw)
In-Reply-To: <8ce556135d6366aeb434794e7247e8ca806ea736.camel@gmail.com>
On Sat, 2022-07-23 at 13:31 +0530, Vibhav Pant via Jit wrote:
> 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.
Good catch!
Do you have push rights to the git repo, or should I push this?
Thanks
Dave
next prev parent reply other threads:[~2022-07-25 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 8:01 Vibhav Pant
2022-07-25 23:18 ` David Malcolm [this message]
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=56d23606ae0212b3077bd617797ab14c465c6cc1.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
--cc=vibhavp@gmail.com \
/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).