Hi there! I'm (still) using the 2006-05-02 build of mspgcc (to avoid surprises, it's used in a productivity environment) under WinXP. Yesterday I installed the latest build (2008-12-30). Mainly because I plan to migrate to the 5436 processor and wanted to check whether mspgcc supports it.
While I had to learn that the extended memory range isn't supported yet (well, one can stick with all the stuff in the lower 64K and just use the extended hardware modules for a lower price), I noticed that the latest version of mspgcc doen't like my makefiles. I always use the -save-temps option to keep the temporary files for debugging and delete them right after compilation. In case of a compiler error, make stops before deleting them. A convenient way to not clobber the code folder with unnecessary files while having them when necessary. To my surprise, the latest compiler produces empty object files if I delete the temp files. I I do not delete them, all is well, but if I delete them (even manually after the compiling and linking is done), the next compilation run results in an empty object file and a list file that reads 'no symbols, no code'. Does anyone know why this is happening now? Of course I can remove the option from the makefile and insert it only when necessary, but I don't like the idea of constantly changing the makefile - as well as I don't like all the temporary files clobbering my source folder(s). For now, I have switched back to the old compiler, but when I ever want to use the newwer processors, I have to switch sooner or later (and pray that the new compiler won't break the old code through new and unexpected optimisations), so this change in the compiler behaviour is still an issue for me. Any comments or hints or explanations are welcome. And sorry that I didn't scan the last 3 years of the mail archive for a mail that fits. I just checked the last 2 months and found nothing. JMGross
