On 11/11/15 08:38, Chris Johns wrote:
On 10/11/2015 11:56 pm, Sebastian Huber wrote:

On 08/11/15 01:05, Chris Johns wrote:
Are there any architecture regressions with gcc-6?
m32c, moxie, v850 don't work with GCC 6.
I thought moxie was building with a new binutils.

/scratch/git-rtems-source-builder/rtems/build/moxie-rtems4.12-gcc-6-20151101-newlib-2.2.0.20151023-x86_64-linux-gnu-1/build/./gcc/xgcc -B/scratch/git-rtems-source-builder/rtems/build/moxie-rtems4.12-gcc-6-20151101-newlib-2.2.0.20151023-x86_64-linux-gnu-1/build/./gcc/ -nostdinc -B/scratch/git-rtems-source-builder/rtems/build/moxie-rtems4.12-gcc-6-20151101-newlib-2.2.0.20151023-x86_64-linux-gnu-1/build/moxie-rtems4.12/newlib/ -isystem /scratch/git-rtems-source-builder/rtems/build/moxie-rtems4.12-gcc-6-20151101-newlib-2.2.0.20151023-x86_64-linux-gnu-1/build/moxie-rtems4.12/newlib/targ-include -isystem /scratch/git-rtems-source-builder/rtems/build/moxie-rtems4.12-gcc-6-20151101-newlib-2.2.0.20151023-x86_64-linux-gnu-1/gcc-6-20151101/newlib/libc/include -B/build/rtems-4.12/moxie-rtems4.12/bin/ -B/build/rtems-4.12/moxie-rtems4.12/lib/ -isystem /build/rtems-4.12/moxie-rtems4.12/include -isystem /build/rtems-4.12/moxie-rtems4.12/sys-include -g -O2 -mel -O2 -I../../../../gcc-6-20151101/libgcc/../newlib/libc/sys/rtems/include -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -I. -I. -I../../.././gcc -I../../../../gcc-6-20151101/libgcc -I../../../../gcc-6-20151101/libgcc/. -I../../../../gcc-6-20151101/libgcc/../gcc -I../../../../gcc-6-20151101/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -o _absvdi2.o -MT _absvdi2.o -MD -MP -MF _absvdi2.dep -DL_absvdi2 -c ../../../../gcc-6-20151101/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
/tmp/ccvr1zIL.s: Assembler messages:
/tmp/ccvr1zIL.s:20: Error: unknown opcode sub $r3,$r2
make[4]: *** [_ashrdi3.o] Error 1
make[4]: *** Waiting for unfinished jobs....
/tmp/cc3BXMUK.s: Assembler messages:
/tmp/cc3BXMUK.s:20: Error: unknown opcode sub $r3,$r2
/tmp/cc5UNxWK.s: Assembler messages:
/tmp/cc5UNxWK.s:26: Error: unknown opcode sub $r1,$r2
make[4]: *** [_lshrdi3.o] Error 1
make[4]: *** [_negdi2.o] Error 1
/tmp/cclz1cLL.s: Assembler messages:
/tmp/cclz1cLL.s:20: Error: unknown opcode sub $r3,$r2
make[4]: *** [_ashldi3.o] Error 1
/tmp/cc2hrdNK.s: Assembler messages:
/tmp/cc2hrdNK.s:43: Error: unknown opcode mul $r12,$r6
/tmp/cc2hrdNK.s:46: Error: unknown opcode mul $r8,$r6
/tmp/cc2hrdNK.s:48: Error: unknown opcode mul $r4,$r7
/tmp/cc2hrdNK.s:50: Error: unknown opcode mul $r1,$r7
/tmp/cc2hrdNK.s:52: Error: unknown opcode add $r1,$r8
/tmp/cc2hrdNK.s:59: Error: unknown opcode add $r3,$r1
/tmp/cc2hrdNK.s:65: Error: unknown opcode add $r4,$r1
/tmp/cc2hrdNK.s:73: Error: unknown opcode add $r1,$r4
/tmp/cc2hrdNK.s:86: Error: unknown opcode mul $r0,$r4
/tmp/cc2hrdNK.s:90: Error: unknown opcode mul $r2,$r4
/tmp/cc2hrdNK.s:92: Error: unknown opcode add $r0,$r2
/tmp/cc2hrdNK.s:96: Error: unknown opcode add $r0,$r12
/tmp/cc2hrdNK.s:97: Error: unknown opcode add $r1,$r2
make[4]: *** [_muldi3.o] Error 1

I already use Binutils 2.25.


epiphany and or1k still use non-FSF GCC.

Great.

What archs have to actually run?
arm, powerpc, sparc.

I am happy to move to gcc-6 for archs we know are working. For those
that do not I am not so sure we should move them.
The broken targets use the 4.11 configuration.

If there is no arch regressions I am happy with this.

Can you please change the version default in rtems-tools?

Does this break 4.11?

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to