On head, the bug is present; the third compilation fails. So sometime between 3b5c6a1def63320a24c45294afa873fde9194625 (August 24) and now the bug was introduced.
I guess it's time to try git bisect. On Fri, Sep 18, 2009 at 4:24 PM, Chris Hanson <c...@chris-hanson.org> wrote: > My mistake: I forgot I was testing the sources from commit > 3b5c6a1def63320a24c45294afa873fde9194625. They appear to be fine. > I'm now running the same test on HEAD. > > On Fri, Sep 18, 2009 at 3:24 PM, Chris Hanson <c...@chris-hanson.org> wrote: >> Yeah, I'm running a test now starting from the 20090107 binary and >> compiling sources from head, and the second compilation is going fine. >> I'm wondering if there's something wrong with my current binary (and >> how that could happen). >> >> On Fri, Sep 18, 2009 at 3:16 PM, Taylor R Campbell <campb...@mumble.net> >> wrote: >>> Date: Fri, 18 Sep 2009 17:58:28 -0400 >>> From: Taylor R Campbell <campb...@mumble.net> >>> >>> Yikes. And I thought that my two-iteration build for testing before >>> pushing would suffice, but it didn't turn this up, because I'm >>> starting with an image made 2009-02-24, building the current sources, >>> and then building them again using the newly built compiler. I guess >>> I'll bump that to a three-iteration build and see what happens. >>> >>> Even on the third iteration, I can't repeat this. I don't think a >>> fourth would be all that useful. >>> >> > _______________________________________________ MIT-Scheme-devel mailing list MIT-Scheme-devel@gnu.org http://lists.gnu.org/mailman/listinfo/mit-scheme-devel