Not sure about that. I'm doing the bisection now. The bug isn't
present in commit 745a16218a43692d2c9ecdad72d1bab73fab0522 from Sept.
7, so it's pretty recent.
On Fri, Sep 18, 2009 at 8:35 PM, Joe Marshall wrote:
> On Fri, Sep 18, 2009 at 1:57 PM, Chris Hanson wrote:
>> FYI, while testing my m
On Fri, Sep 18, 2009 at 1:57 PM, Chris Hanson wrote:
> FYI, while testing my most recent changes, I ran across a recent
> compiler bug. To reproduce: using the current compiler, do a fresh
> compile from sources. Then use that compiler to do another fresh
> compile. The second compilation hangs
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 wrote:
> My mistake: I forgot I was testing the s
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 wrote:
> Yeah, I'm running a test now starting from the 20090107 binary and
> compilin
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 wrote:
> Dat
Date: Fri, 18 Sep 2009 17:58:28 -0400
From: Taylor R Campbell
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 buildi
Of all the recent changes that I'm aware of, I'm thinking that the change
I made to expand the CAR/CDR calls in list.scm is the most likely
culprit just because it is the file `list.scm'. I can't really imagine what
would cause the effect you are seeing, though. I just changed calls
to CADR into
Date: Fri, 18 Sep 2009 13:57:48 -0700
From: Chris Hanson
FYI, while testing my most recent changes, I ran across a recent
compiler bug. To reproduce: using the current compiler, do a fresh
compile from sources. Then use that compiler to do another fresh
compile. The second co
FYI, while testing my most recent changes, I ran across a recent
compiler bug. To reproduce: using the current compiler, do a fresh
compile from sources. Then use that compiler to do another fresh
compile. The second compilation hangs during the compilation of
"cref/anfile" (the very first file
