On Saturday 20 June 2009, Rick Altherr wrote: > I agree that fixing all the portability issues isn't easy and isn't > strictly necessary for any particular future release. I'd just like > to see us progress in that direction when making fixes for data > types. If you need to fix a printf for some other reason, use the > correct format string or macro for the data type in use. It doesn't > take any extra time and makes full portability much easier.
Given this email discussion it evidently *does* take extra time. ;) As I said, I won't object to such fixes. But at the same time, it's worth realizing that it's been quite a few years since much general purpose code has worked on 16-bit CPUs. Even Intel is working on moving away from BIOS boot code that must running on 80286 class CPUs. So I would not put such things on *my* priority list. I believe that OpenOCD could be useful for *TARGET* chips that don't have 32-bit words ... microcontrollers like AVR8, MSP430, and maybe even some subset of the PIC chaos. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
