public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Andrea Corallo <andrea.corallo@arm.com>
Cc: jit@gcc.gnu.org, nd@arm.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgccjit: Add new gcc_jit_context_new_blob entry point
Date: Fri, 24 Jul 2020 18:12:22 -0400	[thread overview]
Message-ID: <22479e6a6a1e27df07a3d2c2cfb8c6c8420a7d3d.camel@redhat.com> (raw)
In-Reply-To: <93e3d65a0b04b13a5d5c9970a2058d167357ed6c.camel@redhat.com>

On Fri, 2020-07-24 at 18:05 -0400, David Malcolm via Gcc-patches wrote:

[...]

> I haven't thought this through in detail, and I'm not sure exactly
> how
> it would work for arbitrary types, but I thought it worth sharing. 
> (For example I can think of nasty issues if we ever want to support
> cross-compilation, e.g. where sizeof types or  endianness differs
> between host and target).

...which is an argument in favor of retaining the name "blob", perhaps
as the name of the argument in the header file e.g.:

extern void
gcc_jit_global_set_initializer (gcc_jit_lvalue *global,
                                 const void *blob,
                                 size_t num_bytes);
 

as a subtle hint to the user that they need to be wary about binary
layouts ("here be dragons").

[...]


  reply	other threads:[~2020-07-24 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 10:11 Andrea Corallo
2020-06-03 15:03 ` David Malcolm
2020-06-03 16:36   ` Andrea Corallo
2020-07-01 16:14     ` Andrea Corallo
2020-07-14 10:00       ` Andrea Corallo
2020-07-24 22:05       ` David Malcolm
2020-07-24 22:12         ` David Malcolm [this message]
2020-08-03  8:07           ` Andrea Corallo
2020-08-06 19:53             ` David Malcolm
2020-08-19  7:17               ` [PATCH V2] " Andrea Corallo
2020-09-09  7:51                 ` Andrea Corallo
2020-09-10 22:22                 ` David Malcolm
2020-09-11 10:31                   ` Andrea Corallo
2020-09-11 11:27                     ` 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=22479e6a6a1e27df07a3d2c2cfb8c6c8420a7d3d.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=andrea.corallo@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@gcc.gnu.org \
    --cc=nd@arm.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).