Ethan Dicks wrote: > define a double-BRK as a noop or a call to the monitor. With this scheme, > you don't have to worry about kernel jump tables in ROM or any of that ugly > stuff. Porting to a different 6502 design is a matter of hardware specific > routines and a vector table that is known to the interrupt handler. Yes, but IMHO the BRK instruction is slow. Together with getting the vector from the BRK address on the stack, then jumping to this address, with saving registers along the way (during the vector get) etc. This is _much_ slower than a simple jump table. <self-plug> And my relocatable file format easily allows 'late-binding', i.e. relocation of jump tables for example at load time </self-plug> Andre -- Email address may be invalid. Use "fachat AT physik DOT tu-chemnitz DOT de" ------Fight SPAM - join CAUCE http://www.cauce.org------Thanks, spammers... Andre Fachat, Institute of physics, Technische Universitšt Chemnitz, FRG http://www.tu-chemnitz.de/~fachat - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail firstname.lastname@example.org.
Archive generated by hypermail 2.1.1.