public inbox for
 help / color / mirror / Atom feed
From: Kay Zheng <>
To: Per Bothner <>
Cc: Kawa mailing list <>
Subject: Re: The "--no-inline" option caused Kawa to generate invalid bytecode
Date: Tue, 05 Sep 2017 16:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

2017-09-05 11:28 GMT+08:00 Per Bothner <>:
> aload_0 does not necessarily means to read the argument array.
> It means to push the contents of local variable 0 (which must
> be a reference to an object or null) onto the operand stack.
> The first few local variables are commonly used for parameters,
> but <clinit> takes no parameters, not even the implicit 'this'.

Indeed I mistook the meaning of the aload_0 instruction, I'm sorry.
Thank you for

  reply	other threads:[~2017-09-05 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 10:25 Kay Zheng
2017-09-05  3:28 ` Per Bothner
2017-09-05 16:51   ` Kay Zheng [this message]
2017-10-05  6:29 ` Per Bothner

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).