This may cause weird errors, depending on your use of the needs_destroy opcode. Because nothing currently sweeps up early_GC PMCs, they may exist somewhere in your object graph. That does allow an interesting debugging possibility, however: mark such PMCs and catch the exceptions to see if you have references to them from places you don't expect. Note that a couple of the t/op/gc.t tests fail. Those failures make sense to me, but the tests themselves don't. A little more sanity there might make the intentions more obvious.
…, it's unused and, evidently, useless.
…d2 Abstract' and the '=head2 Synopsis' command paragraphs in most, but not all, of the pdds.
… not the declaration
…eases.html' in preparation of tomorrow's release.
…re-bootstrap prt0.pir to account for the change in Interpinfo_enum numbering following recent changes. Update prt0.winxed to include the new copyright date (should be dynamic?) so re-bootstrapping does not alter the copyright message. kid51++ for pointing out the test failure.