Well, I tried compiling it with the GCC that comes with the latest binaries on the MSPGCC website, and I had to remove the '_entry' to make it work, since the compiler was adding '_entry' string of its own. Cheers, m.
-----Original Message----- From: mspgcc-users-ad...@lists.sourceforge.net [mailto:mspgcc-users-ad...@lists.sourceforge.net] On Behalf Of Indrek Rebane Sent: Saturday, March 13, 2004 12:56 PM To: mspgcc-users@lists.sourceforge.net Subject: Re: [Mspgcc-users] GCC 3.4 and Frame_Size Milos Prokic wrote: > Hey Oleg... just a side point.... U should update your SOS > website because the "quick fix" you have there is asm > volatile("sub #.L__FrameSize_entry"__FUNCTION__",r1" : :); > (change __FrameSize_entry -> __FrameSize_ ) No, it should be with _entry for task definitions due the way task functions are named in SOS. Not so with interrupt functions. This is fixed in gcc-current. Reason why this statement does not work with GCC 3.4 is in way of handling __FUNCTION__ or __func__ according to C99, which is now char[] variable and you can't concatenate it with string literal. Indrek -- Indrek Rebane | Borthwick-Pignon Electronics Engineer | Tartu Science Park Phone: (+372) 7 302 641 | Riia 185, 51014 Tartu Fax: (+372) 7 383 041 | Estonia ind...@bps.co.ee | www.bps.co.ee ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
