From: Paul Mundt <lethal@linux-sh.org>
To: Jan Dittmer <jdi@l4x.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Trivial sh64 updates for 2.6.23-rc1
Date: Sat, 21 Jul 2007 00:15:43 +0900 [thread overview]
Message-ID: <20070720151543.GA28274@linux-sh.org> (raw)
In-Reply-To: <46A0C199.8050401@l4x.org>
On Fri, Jul 20, 2007 at 04:07:21PM +0200, Jan Dittmer wrote:
> 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).
I've been using sh64-linux targetted toolchains created from the gentoo
crossdev, which works fine with stock versions. I can send you a tarball
of the toolchain off-list if you like.
Applications are still in a pretty questionable state with recent
compilers, but the kernel does hold up well enough.
next prev parent reply other threads:[~2007-07-20 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 9:17 [GIT PULL] Trivial sh64 updates for 2.6.23-rc1 Paul Mundt
2007-07-20 14:07 ` Jan Dittmer
2007-07-20 15:15 ` Paul Mundt [this message]
2007-07-22 11:18 ` Jan Dittmer
2007-07-22 11:42 ` Paul Mundt
2007-07-22 16:39 ` Jan Dittmer
2007-07-22 20:41 ` Paul Mundt
2007-07-23 6:38 ` Jan Dittmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070720151543.GA28274@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.