OK. First about the patches. 01_disable-ffunction-section_warning.patch and 03_FUNCTION-warning-disable.patch apply cleanly to the freshly checked-out cvs, and do not fix the crashing. The other two patches don't apply cleanly, and I didn't spend a lot of time fixing the rejected hunks, but due to your latest message, I doubt that the patches are the responsible for your compiler stability.
The crashing I described in the email was based off of current CVS sources. I have since moved to the prepackaged version at http://www.tinyos.net/tinyos-2.x/doc/html/install-tinyos.html More specifically, I'm using the msp430tools-gcc-3.2.3-20050607.i386 package. This is much older than the cvs, but works with -mdisable-hwmul, as you suggested. The CVS would crash for me with all various optimization settings. The packaged version does not crash with -O0 but does die with any optimization enabled: $ msp430-gcc -mmcu=msp430x149 -o /tmp/ccFpbaoU.o -c code.c -Os code.c:2598: warning: inline function `XE1205SendReceiveP___signalPacketReceived___runTask' given attribute noinline code.c:6845: warning: inline function `XE1205SendReceiveP___signalPacketReceived___runTask' given attribute noinline code.c: In function `Xe1205SpiNoDmaP___0___SpiPacket___send': code.c:8754: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. $ Even though this crash is claimed to be a segmentation fault, instead of an internal error, I'm pretty confident that the two really are the same problem, since replacing return &PropagationMsgPoolP___0___data[idx]; with return 0; on line 6863 of code.c fixes the crash in both the packaged and cvs versions of gcc. Let me know if you can replicate this. No clue as to why you can build with the latest CVS. What if you turn on optimizations? Dima On Fri, 20 Jun 2008 22:02:23 +0200 Hardy Griech <[email protected]> wrote: > Hardy Griech wrote: > : > > Hope you get mspgcc compiled and after that your code.c. BTW it > > would be great, if you could isolate which one of the patches > > actually solves your problem. > : > > Funny, I've compiled the current CVS gcc3.3 with the gcc3.2.3 sources > and your code.c still compiles without crash. > > So my question: what version of msp430-gcc do you have? > > Hardy > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
