On Tue, Mar 12, 2002 at 12:33:26PM +0000, Christophe Rhodes wrote:
> Attached is a patch that fixes format ~/foo::bar/ (which is allowed --
> see 126.96.36.199 in the hyperspec) and adds tests for this (and other
> combinations that could conceivably regress in the future).
OK, I've merged that in sbcl-0.7.1.37.
> Another patch is included more for information than anything --
> removing the descriptor-reg SCs from the CHECK-BOUND vop in
> x86/array.lisp seems to allow that file to compile without error[*],
> and build; I haven't tested rebuilding capability, but I'd be
> surprised if there were a problem. I'm not certain that this is the
> correct fix, though, as the restrictions on the arguments to the VOP
> aren't the same as in the sparc and alpha ports, where, incidentally,
> the corresponding file builds without error currently.
I couldn't convince myself that this is right either. It's not that it
looks questionable, just that it would take a while to immerse myself
in the nuances of register classes before I could say anything
meaningful about it one way or the other. Since the current problem
(bogus warnings) doesn't seem particularly dangerous, and since
neither of us is quite sure, I didn't merge this second patch, but
instead added it as a comment to help when someone returns to the
problem in the future.
William Harold Newman <william.newman@...>
"Of course, if I dig my house foundations by biting the earth while banging
my own head with a spade, then upgrading to mechanical digger maybe won't
help..." -- Graham Perkins <gperkins@...> in comp.lang.eiffel
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C