--target=v850-unknown-elf for c, c++ and java?

2005-08-13 Thread Torsten Mohr
Hi, i try to set up an extended tool chain for --target=v850-unknown-elf. I configured and installed binutils-2.16, that went fine. Configuring and building gcc-3.4.4, gcc-4.0.1 all fail at libstdc++-v3. It seems that there is no "atomic operation provided for this system": configure: WARNING:

Re: --target=v850-unknown-elf for c, c++ and java?

2005-08-13 Thread Torsten Mohr
Hi, thanks for your hints! Sorry for being unclear in my first mail. You were right, it was the C library that was missing. As i've provided newlib now, i now got a working compiler for C, C++ and Java. Best regards, Torsten.

Re: --target=v850-unknown-elf, linker problem

2005-08-15 Thread Torsten Mohr
Hi, > To my untrained eye, this looks a little like a bug. In > v850/lib1funcs.asm, .L_return_interrupt should IMHO be in the > .call_table_text section, not .text. (Would you like to try making the > change? It's still line 1459 in 3.4.4) We might be able to sneak in a > fix before the experts ar

Re: --target=v850-unknown-elf, linker problem

2005-08-16 Thread Torsten Mohr
Hi, > I've taken the liberty of cleaning up the L_callt_save_interrupt > #ifdef, making it consistent with the following one for > L_callt_save_all_interrupt. (This not only removes the .text error, but > adopts the easier to handle layout of the latter.) > Would you mind applying the attached pa

V850 ABI?

2005-08-21 Thread Torsten Mohr
Hi, from gcc-3.4.4/gcc/config/v850/v850.h i got some ideas about the registers (#defs REGISTER_NAMES and ADDITIONAL_REGISTER_NAMES) and about the use of them from the comments to #def REG_ALLOC_ORDER. In that file i've also read about an option "ghs", does that one switch to the Greenhills ABI?