i'd imagine you could either supply a git commit of your compiler in question and the commit itself as well as its parent would be checked out, or you could supply a commit of the compiler and a folder full of patches (this would probably need to know about "sub-compilers" like nqp and the VM for parrot and moarvm). then it'd build and time the two given versions and finally output an html graph comparison, perhaps even including diffs between the commits (this could just use github for displaying the diff, but it should also know about NQP_REVISION and MOAR_REVISION and friends)
i'd imagine you could either supply a git commit of your compiler in question and the commit itself as well as its parent would be checked out, or you could supply a commit of the compiler and a folder full of patches (this would probably need to know about "sub-compilers" like nqp and the VM for parrot and moarvm). then it'd build and time the two given versions and finally output an html graph comparison, perhaps even including diffs between the commits (this could just use github for displaying the diff, but it should also know about NQP_REVISION and MOAR_REVISION and friends)