public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: David Malcolm <dmalcolm@redhat.com>, jit@gcc.gnu.org
Subject: Re: wish: gcc_jit_type_get_atomic
Date: Fri, 01 Jan 2016 00:00:00 -0000	[thread overview]
Message-ID: <57355699.7050701@starynkevitch.net> (raw)
In-Reply-To: <1463083609.11310.81.camel@redhat.com>

On 05/12/2016 10:06 PM, David Malcolm wrote:
> On Thu, 2016-05-12 at 07:48 +0200, Basile Starynkevitch wrote:
>> Hello all,
>>
>> GCC JIT has gcc_jit_type_get_volatile to support the volatile
>> qualifier.
>>
>> But shouldn't it also have a gcc_jit_type_get_atomic to support the
>> C11
>> _Atomic qualifier?
>> http://en.cppreference.com/w/c/atomic
[...]
>>
>> Client code might be able to implement it without explicit libgccjit support by generating calls to the relevant builtins "by hand".

Then perhaps at least that should be a relevant example in the 
documentation about how to
actually use GCC builtins in GCCJIT. Notice that 
gcc_jit_context_get_builtin_function is barely document, and it would be 
nice to have, in 
https://gcc.gnu.org/onlinedocs/jit/topics/functions.html notably, a 
small example (which could be some atomic thing).

Cheers.


-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***

      reply	other threads:[~2016-05-13  4:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  0:00 Basile Starynkevitch
2016-01-01  0:00 ` Basile Starynkevitch
2016-01-01  0:00   ` Basile Starynkevitch
2019-01-01  0:00   ` Marc Nieper-Wißkirchen
2016-01-01  0:00 ` David Malcolm
2016-01-01  0:00   ` Basile Starynkevitch [this message]

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=57355699.7050701@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=dmalcolm@redhat.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).