Hi,

with the examples and that macro in an interrupt function it's the same strange 
warning.

Regards,

Rolf


[email protected] schrieb am 01.07.05 04:09:39:
> 
> The _BIC_SR_IRQ macro doesn't make sense outside interrupt functions.  The
> normal way to make a interrupt function that wakes up the processor is with
> something like:
> 
> interrupt (TIMERA0_VECTOR) wakeup TimerRoutine(void) { ... };
> 
> http://mspgcc.sourceforge.net/manual/x918.html
> 
> mvh.,
> 
> David
> 
> 
> >
> > Hi,
> >
> > i've got a strange problem with _BIC_SR_IRQ: With the file tmp.c with only
> this include and foo function:
> >
> > #include <io.h>
> > void foo (void)
> > {
> >   _BIC_SR_IRQ (LPM4_bits);
> > }
> >
> > and this command line
> >
> > msp430-gcc -mmcu=msp430x168 -O2 -Wall -g  -c -o tmp.o tmp.c
> >
> > the warning
> >
> > tmp.c: In function `foo':
> > tmp.c:4: warning: concatenation of string literals with __FUNCTION__ is
> deprecated
> >
> > is produced.
> >
> > Any ideas?
> >
> > Regards,
> >
> > Rolf
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Mspgcc-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> >
> >
> >
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Reply via email to