The design specification design specification for 20-bit support in mspgcc has been updated:
https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Gcc47:20-Bit_Design The significant changes are: * Add -misr20 to preserve 20-bit registers only in functions that are marked as interrupt handler. This may reduce memory in situations where 20-bit registers are used in isolated areas but with interrupts enabled. * Placement of function and data objects in near or far memory will use declaration attributes instead of named address spaces. Turns out that named address spaces can't be applied to functions, and won't work in C++. * Define the roll-up options for the memory models. "small" is everything in 16 bits. "medium" allows code to use 20-bits, but all data is in near memory. "large" places both code and data in near memory and uses 20-bit pointers for both, but the size types remain 16 bits. "huge" uses 20-bit pointers and 20-bit size types. Interested parties are invited to read the document on the wiki, and comment on this mailing list. Implementation is proceeding nicely, with 20-bit code fairly solid, after fixing a fundamental issue where gcc does not accommodate a system where sizeof(void*) != sizeof(void(*)(). The first release will be in a few weeks. Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
