From: Simon Feltman <s.feltman@gmail.com>
To: jit <jit@gcc.gnu.org>
Subject: Re: Python API (was Re: Build errors)
Date: Tue, 01 Jan 2013 00:00:00 -0000 [thread overview]
Message-ID: <CACc9j8ae+=s08a+Xbw6PEsVH9dPSGN6yntigHoErtJz+94S7tA@mail.gmail.com> (raw)
In-Reply-To: <CACc9j8ZHuSHUYUj3mZ_T3d1DOaoGcpg-Ja4saePY12mundFO0A@mail.gmail.com>
On Wed, Oct 23, 2013 at 10:20 PM, Simon Feltman <s.feltman@gmail.com> wrote:
> ... This is well beyond my knowledge of compiler architecture,
> but it seems like this could be cleaner?
>
> the_type = ctxt.get_type(gccjit.Type.INT)
> local_i = fn.new_local(the_type, b"i")
>
> could be:
> local_i = fn.new_local(gccjit.Type.INT, b"i")
Digging into this a bit more, it looks like the gccjit API is sort of
synthesizing the context dependence for types anyhow. e.g. gcc
internals already seem to be defining the type nodes as globals
(uint64_type_node). So perhaps the API is attempting to present a new
model which the implementation may morph into?
next prev parent reply other threads:[~2013-10-24 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 0:00 Simon Feltman
2013-01-01 0:00 ` Simon Feltman [this message]
2013-01-01 0:00 ` gcc_jit_context (was Re: Python API (was Re: Build errors)) David Malcolm
2013-01-01 0:00 ` Basile Starynkevitch
2013-01-01 0:00 ` Python API (was Re: Build errors) 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='CACc9j8ae+=s08a+Xbw6PEsVH9dPSGN6yntigHoErtJz+94S7tA@mail.gmail.com' \
--to=s.feltman@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).