Jon Zeppieri
2013-10-01 20:41:29 UTC
[Apologies to the list admin who probably received a couple of these
already, as I've been fighting with the mailer daemon.]
I'm attempting to add keyword argument support to the compiler, but
since I'm completely new to the codebase, I have a few questions. I
really appreciate any help you can give me.
First, I wrote a very simple program that (1) defines a method that
takes a keyword argument, and (2) calls it in a loop. I thought that,
if I called the method a sufficient number of times (50?), then the
JIT would kick in and the behavior would change. However, that didn't
happen. When I looked through the code base, I found the line at
ASTCompiler19#compileMethodArgs() that throws a
NotCompilableException. So my first question is:
- Are NotCompilableExceptions caught somewhere, allowing the
interpreter to carry on? (I did a simple grep for this, but didn't
find it.) Or was that code path not taken, at all?
Nest, I AOT-compiled the program and ran it. This time, the program
ran and produced incorrect results. Which leads me to my second
question:
- Does AOT compilation not go through that code path that would throw
the NotCompilableException?
And finally:
- What is the state of the IR? My brief look suggests that currently
the production compiler translates directly from the AST but that
there is a separate, newer compiler pipeline that goes through the IR,
and that pipeline can be turned on with a command-line switch but
which is off by default.
Thanks,
Jon
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
already, as I've been fighting with the mailer daemon.]
I'm attempting to add keyword argument support to the compiler, but
since I'm completely new to the codebase, I have a few questions. I
really appreciate any help you can give me.
First, I wrote a very simple program that (1) defines a method that
takes a keyword argument, and (2) calls it in a loop. I thought that,
if I called the method a sufficient number of times (50?), then the
JIT would kick in and the behavior would change. However, that didn't
happen. When I looked through the code base, I found the line at
ASTCompiler19#compileMethodArgs() that throws a
NotCompilableException. So my first question is:
- Are NotCompilableExceptions caught somewhere, allowing the
interpreter to carry on? (I did a simple grep for this, but didn't
find it.) Or was that code path not taken, at all?
Nest, I AOT-compiled the program and ran it. This time, the program
ran and produced incorrect results. Which leads me to my second
question:
- Does AOT compilation not go through that code path that would throw
the NotCompilableException?
And finally:
- What is the state of the IR? My brief look suggests that currently
the production compiler translates directly from the AST but that
there is a separate, newer compiler pipeline that goes through the IR,
and that pipeline can be turned on with a command-line switch but
which is off by default.
Thanks,
Jon
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email