-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Timothy" == Timothy Stack <[EMAIL PROTECTED]> writes:
Timothy> On Mar 5, 2004, at 4:24 PM, Casey Marshall wrote: >> This solution is obviously a hack; Timothy> I don't think so, it should always be pretty easy for the Timothy> backend to map the regno value to whatever needs to be put in Timothy> the instruction. Since the machine code emitter believes that these numbers can be written into instructions as-is, I doubt that they should be changed. (That is, of course, unless it can no longer be assumed that regno is a valid part of an instruction) >> the correct fix is probobly to fix register.c to not assume that >> regno is an index into reginfo. Timothy> I'm hesitant to mess with the register allocator too much, Timothy> especially since it might break the other backends... I think it should be easy (FLW) to rework the register allocation without damaging the way register-sparse machines work by assuring that the behavior visible from those sides is the same. Besides, my current belief is that this is just the confusion between the SlotData.regno and kregs.regno. But yeah, messing with stuff that is known to work elsewhere is something I'd rather not do. - -- Casey Marshall || [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQFASmMZgAuWMgRGsWsRArniAJ91a619PYrS9RWC3SI27UQiNImJuQCfd4o4 CiSN+k+kYaD0p2bXcKIfUGg= =sfKZ -----END PGP SIGNATURE----- _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
