John Rose wrote:
> When you call a function of type, say, (B), you are promising that the
> 32-bit int you loaded onto the stack fits into the declared subrange,
> say, -128..127.
>
> (This is a little-known invariant of the verifier. Although all
> primitive arguments and return values are passe
On Aug 25, 2011, at 11:23 PM, Jeroen Frijters wrote:
> I was surprised by this as well (from an implementers point of view), because
> the use of asType is an implementation detail. Normally when you call a
> method taking a boolean/byte/short/char you also load an int onto the stack,
> so why
a great deal of difference, of course.
Regards,
Jeroen
> -Original Message-
> From: mlvm-dev-boun...@openjdk.java.net [mailto:mlvm-dev-
> boun...@openjdk.java.net] On Behalf Of Rémi Forax
> Sent: Thursday, August 25, 2011 20:06
> To: Da Vinci Machine Project
> Subject: B
That's a good suggestion; thanks. -- John
On Aug 25, 2011, at 11:06 AM, Rémi Forax wrote:
> Hi John, hi all,
> several people (2 actually :) ask me how to use a boolean/byte/short/char
> as a bootstrap argument.
>
> As you know, you can't because you can't encode a constant
> boolean/byte/shor
Hi John, hi all,
several people (2 actually :) ask me how to use a boolean/byte/short/char
as a bootstrap argument.
As you know, you can't because you can't encode a constant
boolean/byte/short/char
in the constant pool but only an int and because asType() doesn't do
narrowing primitive conversio
