I reproduced the problem on x86_64 with the latest HEAD, so you
don't need to do any more. I will bisect the git repo to track
down where the problem was introduced. It may take a few days,
depending.
-Matt
