Ok, it did not take til tomorrow!

Here is my command line for the compiler invocation:

hardy:~/src/Motexxxx/Multiplexer> gcc --version
gcc (GCC) 3.3.3 (cygwin special)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

hardy:~/src/Motexxxx/Multiplexer> make telos
mkdir -p build/telos
    compiling xxxxMultiplexer to a telos binary
ncc -o build/telos/main.exe -O1 -I../tos/interfaces -I../tos/system -I../tos/platform/%p -I../Common -I/opt/tinyos-1.x-msp/tos/lib/Queue -I/opt/tinyos-1.x-msp/tos/lib/CC2420Radio -I/opt/tinyos-1.x-msp/tos/lib/Flash -fnesc-target=msp430 -gcc=msp430-gcc -mmcu=msp430x1612 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=telos -fnesc-cfile=build/telos/app.c -board= -I../tos/lib/MultiHopLQI -DSEND_QUEUE_SIZE=20 -DMHOP_QUEUE_SIZE=10 -DDEBUG_BUFSIZE=900 -DTOSH_MAX_TASKS_LOG2=5 -DDEBUG -DDEBUGMSG -DIDENT_PROGRAM_NAME="xxxxMulti" -DIDENT_PROGRAM_NAME_BYTES="72,97,114,116,77,117,108,116,105,0" -DIDENT_USER_HASH=0x8be5ca50L -DIDENT_UNIX_TIME=0x4187b75fL -mstrict-align xxxxMultiplexer.nc -lm d:/u/src/Motexxxx/Common/xxxxPacketM.nc:165:2: warning: #warning "xxxxPacket.FloatToxxxxFloat() für Telos nicht getestet" d:/u/src/Motexxxx/Common/xxxxPacketM.nc:189:2: warning: #warning "xxxxPacket.xxxxFloatToFloat() für Telos nicht getestet" d:/cygwin/opt/tinyos-1.x-msp/tos/lib/CC2420Radio/CC2420RadioM.nc:117: warning: `Send.sendDone' called asynchronously from `sendFailed'
    compiled xxxxMultiplexer to build/telos/main.exe
           35314 bytes in ROM
            4017 bytes in RAM
msp430-objcopy --output-target=ihex build/telos/main.exe build/telos/main.ihex
hardy:~/src/Motexxxx/Multiplexer>

As you can see, the programm is not too small - although it is also not a big one...

Funny: even -O2, -O9 and so on is working with my compiler.

Perhaps you could also send me your app.c and I will try to compile it with my compiler!?

Hardy


PS: use -mstrict-align because otherwise the compiler will generate invalid code in some cases (valid for 3.2.3)

Reply via email to