Parrot is a virtual machine designed to efficiently compile and execute bytecode for dynamic languages. Parrot currently hosts a variety of language implementations in various stages of completion, including Tcl, Javascript, Ruby, Lua, Scheme, PHP, Python, Perl 6, APL, and a .NET bytecode translator. Parrot is not about parrots, though we are rather fond of them for obvious reasons.

GSoC 2014 project - Kick off!

Hey everyone!

I am really happy to announce that my GSoC project has gotten underway! I would first like to thank everybody to have given me this wonderful opportunity to be part of the community.

My project's primary objective is to improve the performance of the method signatures. To get the hang of things and understand how method calls and GC work, I have started working on a task that requires me to optimize GC write barriers in the pmc's (

Re-added imcc optimizations


-O1 and -O2 were previously disabled with some more imcc options. I enabled and fixed all of them. Even -O2 is now stable.

Parrot-libgit2 Final Report

GSoC has come to an end finally and my project is done. The project was about implementing bindings to libgit2. I learned quite a bit about git internals, about how libraries are implemented, and parrot stuff.

I began with a better libgit2 header file parser which then creates the NCI low-level definitions. It was accurate enough so that I've had to update it only once since the mid-term data. There is a also a better unified buildsystem, though there are still rough edges around it.

app-parrot-create weekly report

At this week I was working for update tests and documentation on my project.
On the other hand I'm working on opened issues from dukeleto. Such as

I've done all task that we planed with dukeleto.
The future plans are going to work with issues that remain and deploy for enterprise work.

Final GSoC report

What's done?

A cross compiling nqp-js (running on top of parrot) passes all tests in nqp/t/nqp with the exception of test 49 (which does an equivalent of eval, which would be really tricky do in a cross compiler).
It also passes the serialization tests in nqp/t/serialization.
It also passes the same tests as nqp-parrot in nqp/t/qregex.
We use a custom harness for those to avoid compiling regex at runtime.

A standalone nqp-js (compiled with a cross compiling nqp-js and using a setting compiled by a cross compiling nqp-js) passes most of the tests in nqp/t/nqp (it fails 5 of them).

app-parrot-create weekly report

At this day I have done my work. The last task which I provided it's a build with perl 5 language.

This is a final week at GSoC, so I will plan to write more tests and update documentation.

The last version of my project you can test on

Future plans:
- update API, realization a garbage collector(automatical remove old content) on my app
- realization an automatical deploy system on WebServer

parrot-libgit2 report: References, Trees, Remotes

This was a fairly productive week, with many new features.

GSoc progress report

Got the nqp/t/qregex tests to pass.
It would be a good idead for me to document how the rules engines of the MoarVM, Parrot, JVM and JavaScript backends work.
They are pretty similiar as it's basically the translation of the same code.
Unfortunately some things get cargo culted.
Like parrot registers names ending up in MoarVM code.

This means the rules engines implementation is resonably sane.
Incorrect test description caused a lot of confusion.

app-parrot-create weekly report

At that day my project have almost done. In previous few week I worked over different type of tests. It are Rosella(Winxed), Rosella(NQP) and Perl 5 tests for HLL and library templates. - rosella(winxed) tests on library template - rosella(nqp) tests on library template - perl 5 tests on library template

Parrot-libgit2 report: Using parrot-libgit2

Now that a minimal api is ready, its time that I document how to use it:

Its possible to use the library to deal with repositories, the repository index, low-level object access, commits, revision walking, blobs, git configs and more. Major things that are still not done are dealing with references and trees, which are only waiting on a few issues(mentioned below).

These are rough examples of how to use the major classes.

Opening repositories:

using Git2.Repository;
var repo = new Git2.Repository("/path/to/repository");

Dealing with the index:

Syndicate content