public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bartosz Szreder <bartosz.szreder@huuugegames.com>
To: jit@gcc.gnu.org
Subject: Function pointer handling
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <CACDdPnvRcueTLRWEqxeUZJz5+392Shwt_bSL7WNvgXvFVWFOcA@mail.gmail.com> (raw)

I have some questions regarding pointers to functions in current (7.2)
version of GCC-JIT.

1. The documentation doesn't mention existence of
gcc_jit_context_new_function_ptr_type() as a mechanism of handling
function pointers, yet contains
gcc_jit_context_new_call_through_ptr().

- Is the former function unsupported/buggy in some way and is not
indented for general use, or just lacks proper documentation?

- What is the proper way of obtaining a function pointer to be passed
to gcc_jit_context_new_call_through_ptr()? There doesn't seem to be
any counterpart to gcc_jit_lvalue_get_address() for functions. As the
name suggests, gcc_jit_lvalue_get_address() works on an L-value and
gcc_jit_function type isn't an ancestor of gcc_jit_lvalue in the
internal type system, therefore upcasting is impossible.

2. Is it safe to pass a function pointer as a GCC_JIT_TYPE_VOID_PTR
and use gcc_jit_context_new_call_through_ptr() on such value?

Thanks,
Bartosz Szreder

             reply	other threads:[~2017-09-21 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01  0:00 Bartosz Szreder [this message]
2017-01-01  0:00 ` David Malcolm
2017-01-01  0:00   ` [committed] jit: document function pointers David Malcolm
2017-01-01  0:00   ` Function pointer handling Bartosz Szreder
2017-01-01  0:00     ` [committed] jit: implement gcc_jit_function_get_address 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=CACDdPnvRcueTLRWEqxeUZJz5+392Shwt_bSL7WNvgXvFVWFOcA@mail.gmail.com \
    --to=bartosz.szreder@huuugegames.com \
    --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).