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: [PATCH] Work-in-progress: gcc_jit_type_get_aligned
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <87y3vmse4n.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1490730511-17122-1-git-send-email-dmalcolm@redhat.com> (David Malcolm's message of "Tue, 28 Mar 2017 15:48:31 -0400")

* David Malcolm:

> Here's a work-in-progress implementation of the idea, adding this
> entrypoint to the API:
>
>   extern gcc_jit_type *
>   gcc_jit_type_get_aligned (gcc_jit_type *type,
>                             unsigned int alignment_in_bytes);

Should be size_t, not unsigned int.  A 2**31 alignment isn't as
ridiculous as it might seem.  x86-64 already has a 2**30 alignment
requirement in some contexts.

  reply	other threads:[~2017-03-30 20:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01  0:00 Alignment not supported? 정인배(Inbae Jeong)
2017-01-01  0:00 ` Florian Weimer
2017-01-01  0:00   ` 정인배(Inbae Jeong)
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         ` 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
2017-01-01  0:00     ` [PATCH] Work-in-progress: gcc_jit_type_get_aligned David Malcolm
2017-01-01  0:00       ` Florian Weimer [this message]
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=87y3vmse4n.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).