Found an extremely weird parsing bug involving ">". Note that it doesn't seem to be a simple predence thing -- look at the comments of new t/pugsbugs/parsing_gt.t.