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: <CACXZuxdhVPQNWuQbq+rVaZH_RhYMV3zs9Jnsq97ooMPx9zSySg@mail.gmail.com> (raw)
In-Reply-To: <1434328137.3192.9.camel@surprise>
On 15 June 2015 at 01:28, David Malcolm <dmalcolm@redhat.com> wrote:
> On Sat, 2015-06-13 at 21:25 +0100, Dibyendu Majumdar wrote:
>> On 11 June 2015 at 21:31, David Malcolm <dmalcolm@redhat.com> wrote:
>> > 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).
>> >
>>
>> Can an assignment statement be added to a block that is already terminated?
>
> No; you'll get an error like:
>
> adding to terminated block: entry (already terminated by: goto foo)
>
> So you may want to wait until you've added all the initializations
> before adding the jump from the entry block to the block for the first
> bytecode.
>
I can do that, but maybe I don't need to? If the assignment occurs in
a subsequent block and is valid from control flow point of view then
it is correct - right?
Regards
Dibyendu
next prev parent reply other threads:[~2015-06-15 19:46 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 [this message]
2015-01-01 0:00 ` Dibyendu Majumdar
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=CACXZuxdhVPQNWuQbq+rVaZH_RhYMV3zs9Jnsq97ooMPx9zSySg@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).