public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org
Subject: Re: Basic blocks, jump targets and locals
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <CACXZuxeggPwZHbjPnZ9sjbShpcfdGKApXS8KBSQ1X6xV27sYuQ@mail.gmail.com> (raw)
In-Reply-To: <1434054685.12727.205.camel@surprise>

On 11 June 2015 at 21:31, David Malcolm <dmalcolm@redhat.com> wrote:
>> Can one create several blocks in advance - and set a block that is not
>> yet inserted into the function as the target for a jump?
>
> Yes.  See e.g.:
> https://gcc.gnu.org/onlinedocs/jit/intro/tutorial04.html#populating-the-function
> which does two passes:
> (i) iterates through all of the bytecodes in a function, creating
> gcc_jit_block instances for each one
> (ii) iterates again, populating the gcc_jit_block instances with
> statements
>
>
>> Finally - how are local variable related to blocks. In LLVM one has to
>> create the local vars in the entry block of the function. Is it the
>> same with libgccjit?
>
> Local variables in libgccjit are local to a *function*; there's no
> association between them and blocks.  Blocks in libgccjit relate to
> control flow, not to scope.
>
> Note that any initialization of a local variable has to be done
> explicitly, by adding an assignment statement.  Typically that
> assignment statement would be added to the initial block, as in the
> example above (so I suppose that's an association of sorts between
> locals and the entry block).
>
> Hope this is clear


Thanks Dave - all very clear.

      parent reply	other threads:[~2015-06-11 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 Dibyendu Majumdar
2015-01-01  0:00 ` David Malcolm
2015-01-01  0:00   ` David Malcolm
2015-01-01  0:00     ` Dibyendu Majumdar
2015-01-01  0:00   ` Dibyendu Majumdar
2015-01-01  0:00     ` David Malcolm
2015-01-01  0:00       ` Dibyendu Majumdar
2015-01-01  0:00   ` Dibyendu Majumdar [this message]

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=CACXZuxeggPwZHbjPnZ9sjbShpcfdGKApXS8KBSQ1X6xV27sYuQ@mail.gmail.com \
    --to=mobile@majumdar.org.uk \
    --cc=dmalcolm@redhat.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).