public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: David Malcolm <dmalcolm@redhat.com>
Cc: "정인배(Inbae Jeong)" <kukyakya@gmail.com>, jit@gcc.gnu.org
Subject: Re: Alignment not supported?
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <87h92eofuf.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1490630429.11099.60.camel@redhat.com> (David Malcolm's message of "Mon, 27 Mar 2017 12:00:29 -0400")

* David Malcolm:

>> I would suggest to model the interface after gcc_jit_context_new_call
>> (but still keep it separate because even though attributes with
>> arguments are syntactically pretty much like function calls in the C
>> front end, semantically, they are not). 
>
> If I understand you right, this would give something like:
>
> extern gcc_jit_type *
> gcc_jit_type_add_attribute (gcc_jit_type *type
>                             const char *attribute_name,
>                             int numargs, gcc_jit_rvalue **args);

Right.

> Is every attribute arg an rvalue though?  Can some of them be types?

Not sure about that, but the “mode” attribute appears to be special in
this regard.  There could be others.

  parent reply	other threads:[~2017-03-27 16:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01  0:00 정인배(Inbae Jeong)
2017-01-01  0:00 ` Florian Weimer
2017-01-01  0:00   ` 정인배(Inbae Jeong)
2017-01-01  0:00     ` David Malcolm
2017-01-01  0:00       ` Florian Weimer
2017-01-01  0:00         ` David Malcolm
2017-01-01  0:00           ` David Malcolm
2017-01-01  0:00             ` Florian Weimer
2017-01-01  0:00               ` David Malcolm
2017-01-01  0:00                 ` Florian Weimer
2017-01-01  0:00           ` Florian Weimer [this message]
2017-01-01  0:00     ` Florian Weimer
2017-01-01  0:00     ` [PATCH] Work-in-progress: gcc_jit_type_get_aligned David Malcolm
2017-01-01  0:00       ` Florian Weimer
2017-01-01  0:00         ` [PATCH] Add gcc_jit_type_get_aligned David Malcolm
2017-01-01  0:00           ` 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=87h92eofuf.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=dmalcolm@redhat.com \
    --cc=jit@gcc.gnu.org \
    --cc=kukyakya@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).