v0.1.19

A patch release that lets bisections run over a chosen binutils and around known unbuildable stretches, forges old binutils, answers the kernel plan's open question 10 in a report, and confirms more fixing commits by bisection.

Changes:

• gk bisect-kernel takes --binutils B and lays that binutils over the GCC bundle at every step, the way a cell of the binutils sweep does. The record's file name and the runs table name it. (#222)
• Before the first step a bisection marks as skipped every commit that sits inside a known unbuildable stretch, such as the O= breakage between 2244cbd8a918 and 8c7f75d3257f in 2.6.16. (#219)
• reports/bisections.md counts each signature's failing cells, from the newest cell of each crossing, and says how many open entries match no cell yet. (#224)
• A binutils-only bundle uses gcc-3.4 where the forge has it, so binutils 2.14 forges in etch. (#226)
• reports/question-10.md answers open question 10, which 3.x and 4.x branches a later GCC builds, from the last point of each branch, and reports/eras.md links to it. (#227)

Findings:

• gcc48-ptrace-asmregparm (1b4ac2a935aa), gcc-min-81 on arm64 (118c40b7b503) and gcc-min-49 (6ec4476ac825) are confirmed by bisection. gcc3-0-1-refused cannot be, and its note says why. (#220)
• gcc3-vdso-plt-overlap (c65916fe3586) and gcc43-no-unit-at-a-time (9ab34fe76114) are confirmed. (#221)
• gcc-min-32 is fd285bb54d8a, not a136564 as the catalog had it, and gcc-296-frame-pointer names the same commit. (#223)
• gcc42-proxy-pda (1bac3b383a93) is confirmed. (#225)