From: "Marc Nieper-Wißkirchen" <marc.nieper@gmail.com>
To: jit@gcc.gnu.org
Subject: [FEATURE REQUEST] Implement gcc_jit_sig_atomic_type.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <CAEYrNrRvNK6kczWSUFuKYCQLjb8faYAdxDWVS9uhLSiKSbZDBg@mail.gmail.com> (raw)
Each target of gcc defines `SIG_ATOMIC_TYPE', which is then used to
implement the built-in preprocessor macro `__SIG_ATOMIC_TYPE__', which
is then used by <signal.h> to typedef `sig_atomic_t'.
This type is used, for example, when writing POSIX-compliant signal handlers.
It is defined as: "An integer type which can be accessed as an atomic
entity even in the presence of asynchronous interrupts made by
signals."
This is a feature request to expose this type to libgccjit by
providing the following function:
gcc_jit_type *gcc_jit_sig_atomic_type (gcc_jit_context *ctxt)
-- Marc
P.S.: Depending on my spare time, I may be able to write a patch that
would implement this feature request.
reply other threads:[~2019-01-14 15:53 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=CAEYrNrRvNK6kczWSUFuKYCQLjb8faYAdxDWVS9uhLSiKSbZDBg@mail.gmail.com \
--to=marc.nieper@gmail.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).