PICdude wrote 2012-02-19 14:55: > Some years ago I fat-fingered movwf as movfw instead and it compiled > w/o an error. Apparently it's the same as "movf ...,W" and was > leftover from an earlier time. Still works, but I don't use it as > it's undocumented... It's not. See : "A.6 12-BIT/14-BIT INSTRUCTION WIDTH PSEUDO-INSTRUCTIONS" in the MPASM manual. > ...so unsure when/if it'll be dropped. > > Cheers, > -Neil. > > > > Quoting Peter: > >> I found some balky jal generated pic code which was disassembled by >> me to yield >> the use of what appears to be an undocumented instruction, used as in: >> >> 0821 movf 0x21, w ; load w with data from reg. 0x21 >> 0065 tris 0x65 ; undocumented instruction >> >> Target is pic16f628 (non A), disassembler is gpdasm. >> >> Can someone shed some light on this? Jal author (Wouter), gpdasm contrib= utors >> (Scott D.)? Vasile Surducan? >> >> I have the jal source for the above, this is not reverse engineering >> or anything >> like that. >> >> Any more easter eggs in pics we need to know about? Google knows >> next to nothing >> about it, and I suspect any entries might have been censed. >> >> thanks, >> >> -- Peter >> >> >> -- >> http://www.piclist.com PIC/SX FAQ& list archive >> View/change your membership options at >> http://mailman.mit.edu/mailman/listinfo/piclist >> > > > --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .