Hi Peter,

I was trying out the mspgcc uniarch.

I can compile the applications Null, Blink with 'make telosb' and get some 
include warnings.

When i want to compile UDPEcho or PppRouter from trunk with 'make telosb blip', 
I am getting the following internal compilation error:

mab@shelbyville:~/src/external/git/tinyos-main/apps/UDPEcho$ make telosb blip
mkdir -p build/telosb
    compiling UDPEchoC to a telosb binary
ncc -o build/telosb/main.exe  -Os -O -DENABLE_SPI0_DMA -DRPL_ROUTING 
-DRPL_STORING_MODE -I/home/mab/src/external/git/tinyos-main/tos/lib/net/rpl 
-DIN6_PREFIX=\"fec0::\" -
I/home/mab/src/external/git/tinyos-main/tos/lib/printf 
-DCC2420_HW_ACKNOWLEDGEMENTS  -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK 
-DBLIP_L2_RETRIES=3 -
DTOSH_DATA_LENGTH=90 -I/home/mab/src/external/git/tinyos-main/tos/lib/net/ 
-I/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/ 
-I/home/mab/src/external/git/tinyos-
main/tos/lib/net/blip/ 
-I/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/interfaces/  
-I/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/nwprog/ 
-I/home/mab/src/external/git/tinyos-
main/tos/lib/net/blip/shell/ 
-I/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/serial/ 
-I/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/platform/ 
-I/home/mab/src/external/git/tinyos-
main/tos/lib/net/blip/icmp/ 
-I/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/dhcp/ 
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/iovec.c 
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/in_cksum.c 
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/ip_malloc.c
 
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/utility.c 
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/table.c -mdisable-hwmul 
-fnesc-separator=__ -Wall -Wshadow -
Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= 
-DDEFINED_TOS_AM_GROUP=0x22 -Ibuild/telosb -DIDENT_APPNAME=\"UDPEchoC\" 
-DIDENT_USERNAME=\"mab\" -
DIDENT_HOSTNAME=\"shelbyville.com\" -DIDENT_USERHASH=0x8ac94f7eL 
-DIDENT_TIMESTAMP=0x4def5818L -DIDENT_UIDHASH=0xc5a4266bL  UDPEchoC.nc -lm 
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/utility.c: 
In function 'inet_pton6':
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/utility.c:56:1:
 error: unrecognizable insn:
(insn 116 115 117 13 
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/utility.c:27
 (set (mem/s/j:HI (reg/f:HI 114) [0 dest_24(D)->in6_u.u6_addr16 S2 A16])
        (rotate:HI (reg/v:HI 48 [ cur ])
            (const_int 8 [0x8]))) -1 (nil))
/home/mab/src/external/git/tinyos-main/support/sdk/c/blip/lib6lowpan/utility.c:56:1:
 internal compiler error: in extract_insn, at recog.c:2103
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
In file included from 
/home/mab/src/external/git/tinyos-main/tos/chips/msp430/msp430hardware.h:40,
                 from 
/home/mab/src/external/git/tinyos-main/tos/platforms/telosb/hardware.h:4,
                 from 
/home/mab/src/external/git/tinyos-main/tos/system/SchedulerBasicP.nc:52:
/opt/msp430-uniarch/lib/gcc/msp430/4.5.2/../../../../msp430/include/io.h:1:2: 
warning: #warning <io.h> is deprecated, please include <msp430.h>
In file included from 
/home/mab/src/external/git/tinyos-main/tos/chips/msp430/msp430hardware.h:41,
                 from 
/home/mab/src/external/git/tinyos-main/tos/platforms/telosb/hardware.h:4,
                 from 
/home/mab/src/external/git/tinyos-main/tos/system/SchedulerBasicP.nc:52:
/opt/msp430-uniarch/lib/gcc/msp430/4.5.2/../../../../msp430/include/signal.h:43:2:
 warning: #warning msp430-libc <signal.h> deprecated, using <legacymsp430.h>
In file included from 
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/blip_printf.h:17,
                 from UDPEchoP.nc:40,
                 from UDPEchoC.nc:40:
/opt/msp430-uniarch/lib/gcc/msp430/4.5.2/../../../../msp430/include/stdio.h:52: 
warning: empty declaration
/home/mab/src/external/git/tinyos-main/tos/chips/msp430/usart/Msp430Spi0C.nc:99:2:
 warning: #warning "Enabling SPI DMA on USART0"
/home/mab/src/external/git/tinyos-main/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: 
warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"
/home/mab/src/external/git/tinyos-main/tos/chips/cc2420/link/PacketLinkC.nc:38:2:
 warning: #warning "*** USING PACKET LINK LAYER"
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/shell/UDPShellP.nc:248: 
warning: call via function pointer
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/IPNeighborDiscoveryP.nc:
 In function 'IPNeighborDiscoveryP__NeighborDiscovery__resolveAddress':
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/IPNeighborDiscoveryP.nc:90:1:
 error: unrecognizable insn:
(insn 50 49 51 6 
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/IPNeighborDiscoveryP.nc:66
 (set (reg:HI 78)
        (rotate:HI (mem/s/j:HI (plus:HI (reg/v/f:HI 73 [ addr ])
                    (const_int 8 [0x8])) [0 addr_4(D)->in6_u.u6_addr16+8 S2 
A16])
            (const_int 8 [0x8]))) -1 (nil))
/home/mab/src/external/git/tinyos-main/tos/lib/net/blip/IPNeighborDiscoveryP.nc:90:1:
 internal compiler error: in extract_insn, at recog.c:2103
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [exe0] Error 1

If I compile Null or Blink with 'make telosb blip', I am getting the very same 
error.

Markus

> Hmm all right.  That sounds a little tight since we probably won't be able
> to properly test everything with a new compiler; as I understood it we were
> supposed to release by the end of the month.  Sounds like we better start
> moving to the uniarch for our own development and maybe do the release with
> it marked as "experimental," and also make it clear that this will be the
> last release where 3.2.3 is supported.
> 
> Thanks for the insights,
> Steve
> 
> On Tue, Jun 7, 2011 at 6:32 PM, Peter Bigot <[email protected]> wrote:
> > Depends on when 2.1.2 is anticipated.  When uniarch moves to 4.5.3 it
> > will be supported, with bug-fix only releases.  New features (including
> > 20-bit support) will be prototyped in the 4.6.x branches.  Using
> > uniarch-mspgcc-4.5.3-20110701 (or whatever) would be the way I would
> > recommend, rather than hitching your wagon to the dead mspgcc4 horse.
> > 
> > Peter
> > 
> > 
> > On Tue, Jun 7, 2011 at 8:15 PM, Stephen Dawson-Haggerty <
> > 
> > [email protected]> wrote:
> >> I'll give uniarch a try, thanks for the status update.
> >> 
> >> I guess the real question I'm asking is which, if any, of these should
> >> we release with?  I think it's worth having a supported compiler
> >> version since we do hit bugs given we're compiling generated code...
> >> 
> >> Steve
> >> 
> >> On Tue, Jun 7, 2011 at 6:09 PM, Peter Bigot <[email protected]> wrote:
> >>> uniarch mspgcc is the new mspgcc4; there are no plans to release
> >>> another mspgcc4 version, and support and code development has returned
> >>> to the mspgcc project on sourceforge.  We may be within a week or two
> >>> of having uniarch available in the experimental Debian package area,
> >>> for those who don't want to build it by hand (the tinyos community is
> >>> on the list to notify once that happens).  In fact, everything's there
> >>> already except for msp430-libc, where we're still cleaning up
> >>> copyright issues.
> >>> 
> >>> All that's good in mspgcc4 is better in uniarch.  The current master
> >>> branches are based on gcc 4.5.2, but the official first release will be
> >>> based on 4.5.3.
> >>> 
> >>> Peter
> >>> 
> >>> On Tue, Jun 7, 2011 at 4:10 PM, Stephen Dawson-Haggerty <
> >>> 
> >>> [email protected]> wrote:
> >>>> I haven't seen any recent discussion about moving to mspgcc4 for
> >>>> 2.1.2, but I know people are using it and it has significantly better
> >>>> support for upcoming msp revisions.  My question is if this is
> >>>> something we can shift to recommending for the release, since it
> >>>> generates 5-10% smaller code with more coming down the line, and the
> >>>> tree currently is known to work with it at least on telosb and epic.
> >>>> 
> >>>> Perhaps we could "recommend" mspgcc4 (some specific version which we
> >>>> decide) and "deprecate" 3.2.3 for this release, but still test with
> >>>> both compilers with the expectation we will move to the newer one
> >>>> only for future releases?
> >>>> 
> >>>> Steve
> >>>> 
> >>>> --
> >>>> stephen dawson-haggerty
> >>>> http://cs.berkeley.edu/~stevedh
> >>>> uc berkeley wireless and embedded systems lab
> >>>> berkeley, ca 94720
> >>>> 
> >>>> _______________________________________________
> >>>> Tinyos-devel mailing list
> >>>> [email protected]
> >>>> 
> >>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-de
> >>>> vel
> >> 
> >> --
> >> stephen dawson-haggerty
> >> http://cs.berkeley.edu/~stevedh
> >> uc berkeley wireless and embedded systems lab
> >> berkeley, ca 94720
------------------------------------------------
| Dipl.-Ing. Markus Becker
| Communication Networks
| TZI - Center for Computing Technologies
| University Bremen
| Germany
------------------------------------------------
| web: http://www.comnets.uni-bremen.de/~mab/
| mailto: [email protected]
| telephone: +49 421 218 62379
| building: NW1 room: N2260
------------------------------------------------
_______________________________________________
Tinyos-devel mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel

Reply via email to