linux-kernel - Re: [PATCH] arch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53A6EDF6.2030203@roeck-us.net>
Date:	Sun, 22 Jun 2014 07:53:42 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Chen Gang <gang.chen.5i5j@...il.com>,
	Liqin Chen <liqin.linux@...il.com>,
	Lennox Wu <lennox.wu@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_'
 for related macros

On 06/21/2014 10:33 PM, Chen Gang wrote:

[ ... ]

>> Any idea where to find a cross-compile toolchain for this architecture ?
>>
>
> I use latest source code of gcc and binutils with git.
>
>    related source code:
>
>      git://sourceware.org/git/binutils-gdb.git
>      git://gcc.gnu.org/git/gcc.git
>
> Issues:
>
>    For binutils, have to use the latest one (I have fixed one segment
>    fault issue of gas for score, and integrated into gas main line by
>    maintainer in Jun 13, 2014).
>
>    For gcc (after binutils has installed), when building glibc, may need
>    modify the absolute path for score-elf-gas, score-elf-ld ... in
>    related auto-generated file.
>
>    Under ubuntu (but under fedora, it is OK), may need export
>    LD_LIBRARY_PATH=/usr/local/lib for searching libmpfr.so.
>
> My current binary informations:
>
>    root@...en:/upstream/toolchain/binutils-gdb# /usr/local/bin/score-elf-ld -v
>    GNU ld (GNU Binutils) 2.24.51.20140609
>    root@...en:/upstream/toolchain/binutils-gdb# /usr/local/bin/score-elf-as -v
>    GNU assembler version 2.24.51 (score-elf) using BFD version (GNU Binutils) 2.24.51.20140609
>    root@...en:/upstream/toolchain/binutils-gdb# /usr/local/bin/score-elf-gcc -v
>    Using built-in specs.
>    COLLECT_GCC=/usr/local/bin/score-elf-gcc
>    COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/score-elf/4.10.0/lto-wrapper
>    Target: score-elf
>    Configured with: ../gcc/configure --without-header --disable-nls --enable-language=c --disable-threads --disable-shared --enable-werror=no target_configargs=enable_vtable_verify=yes --target=score-elf --enable-obsolete
>    Thread model: single
>    gcc version 4.10.0 20140530 (experimental) (GCC)
>

I did that, and managed to build gcc.

However, when trying to compile score defconfig, I get internal compiler errors in cc1
when compiling drivers/tty/tty_mutex.o and block/elevator.o.

  CC      block/elevator.o
score-elf-gcc: internal compiler error: Segmentation fault (program cc1)
0x40c073 execute
	../../gcc/gcc/gcc.c:2848
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[1]: *** [block/elevator.o] Error 4
make: *** [block/elevator.o] Error 2

Do you see that as well ?

This is with

GNU assembler version 2.24.51 (score-elf) using BFD version (GNU Binutils) 2.24.51.20140622

and gcc configured with:

Configured with: ../gcc/configure --prefix=/opt/kernel/score --program-prefix=score-elf- \
--target=score-elf --without-header --disable-nls --enable-languages=c --disable-threads \
--disable-shared --enable-werror=no target_configargs=enable_vtable_verify=yes \
--enable-obsolete --disable-libssp --disable-libquadmath

Tip of gcc source is commit d8686b0aa945a, tip of binutils source is commit d17c74c1d41.
Your assembler fix is included in this version of binutils.

Thanks,
Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/