> I can't seem to make mspgcc call functions above 64K, not even with > version 4.4.4 Now, this is in the 4.x branch, isn't it?
As far as I know, the only version to support more than 64K is the MSP430X branch in CVS, which is 3.2.3 (it hasn't been merged into 4.x yet). I've used it with the patches from http://www.innoventis.de/downloads/mspgcc/. > Also, starting from version 4, the release notes say "the MSPGCC4 port > fixes the data-sections bug present in all original MSPGCC versions". > Does this mean you don't manually have to relocate functions(i.e. : > moving them to higher addresses >64K for BIG applications) ? Yes and no - you can't automatically use memory above 64K*, but by using -ffunction-sections, you can at least shuffle things around using a linker script (at finer granularity than whole object files). For example, I've toyed with the idea of a script that would put functions starting with A-M into .text, and N-Z into .fartext. It's not exactly an optimal allocation policy, but it beats having to manually annotate every function you want placed in .fartext. * Because the interrupt vectors section is in the middle of code memory and the linker doesn't support sections with holes in, it treats them as separate sections and you have to assign a block of code to either one or the other (with .text as the default). HTH, Michiel ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
