public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Antoni Boucher <bouanto@zoho.com>
To: gcc@gcc.gnu.org
Cc: Guillaume Gomez <guillaume1.gomez@gmail.com>,
	David Malcolm <dmalcolm@redhat.com>
Subject: Handling of nonnull function attribute
Date: Thu, 21 Sep 2023 10:47:58 -0400	[thread overview]
Message-ID: <ce657b2623113a9deef67c21a2282d8e07959b5a.camel@zoho.com> (raw)

Hi.
I'm working on adding the support for the nonnull attribute in
libgccjit.
I found out a way to make it working, but I need more help to find a
proper solution.
The problem is that the nonnull attribute should be added to the
fn_type while we added it to the fn_decl.
If we add it to the fn_type directly, it works.
However, it seems the other frontends do that automatically, by the way
of c_common_attribute_table (field type_required set to true).
Is this correct?
If so, how does this mechanism work and how can it be enabled for a
frontend?
I tried calling init_attributes at the end of jit_langhook_init, but
that doesn't work.
Thanks for your help.

             reply	other threads:[~2023-09-21 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 14:47 Antoni Boucher [this message]
2023-09-21 19:48 ` Guillaume Gomez

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=ce657b2623113a9deef67c21a2282d8e07959b5a.camel@zoho.com \
    --to=bouanto@zoho.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guillaume1.gomez@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).