linux-kernel - Re: [GIT PULL] Trivial sh64 updates for 2.6.23-rc1

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: <46A0C199.8050401@l4x.org>
Date:	Fri, 20 Jul 2007 16:07:21 +0200
From:	Jan Dittmer <jdi@....org>
To:	Paul Mundt <lethal@...ux-sh.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Trivial sh64 updates for 2.6.23-rc1

Paul Mundt wrote:
> Paul Mundt (5):
>       sh64: Wire up fallocate() syscall.
>       sh64: Update cayman defconfig.
>       sh64: Fix up PCI section mismatch warnings.
>       sh64: Move entry point code to .text.head.
>       sh64: Flag sh64_get_page() as __init_refok.

Tangential question. Which is the currently recommended cross toolchain
for sh64? With "gcc 3.2 20020529", "binutils 020306 20030206" (some
binary toolchain from ~2 years ago somewhere off the web) I get [1]

   CC      fs/seq_file.o
   CC      fs/xattr.o
fs/xattr.c: In function `vfs_listxattr':
fs/xattr.c:161: unrecognizable insn:
(insn 162 159 114 (set (subreg:DI (reg:SI 181) 0)
         (reg:DI 182)) -1 (nil)
     (nil))
fs/xattr.c:161: Internal compiler error in get_attr_highpart, at 
insn-attrtab.c:6211
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [fs/xattr.o] Error 1
make[1]: *** [fs] Error 2
make: *** [_all] Error 2

gcc 3.4.x, 4.0.x, 4.1.x don't build for me from source
(target -superh-linux-gnu, binutils 2.15.x or 2.17.x).

Thanks,

Jan

[1] http://l4x.org/k/?d=32100
-
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/