> Peter, > > I have been working on a patch for gcc-4.0.2, and have it compiling now, > > although I have some problems with the machine description file and > > optimisations. I would like to put these into the public cvs so maybe > > someone who knows how to fix it could, or when I get the chance Ill have > > a go at figuring out how to fix the machine description file. > > That's cool! > cause I lost my recent 4.xx updates and have no time to do this again. > Yes, put your sources to cvs and I'll have a look. > > ~d >
It's great to hear that you guys are working on gcc 4.x updates - many thanks for your work. However, I wonder if it is not better to work directly towards 4.1 support, and skip 4.0 altogether? To my understanding, gcc 4.0 exists more as a half-way between the 3.x series and new versions. It provides the re-structuring needed for a whole range of new optomisations and features, but these are not implemented in 4.0. On other targets (such as the AVR), 4.0 has minor improvements for some code, but in many cases produces worse code than 3.4.x. The real difference will be with 4.1, where a number of significant changes have been implemented. For example, with 4.1 it will be possible to compile the whole program as a single lump, allowing very powerful inter-procedural optomisations. As far as I am aware (although I've not had the time to delve into gcc inards), these improvements are all part of the front and middle parts of gcc, and thus should be practicaly free for msp-gcc. gcc 4.1 has not yet been officially released, but is in final regression testing. http://gcc.gnu.org/gcc-4.1/changes.html Regards, David
