This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] enable fdpic targets/emulations for sh*-*-linux*
- From: Rich Felker <dalias at libc dot org>
- To: Alan Modra <amodra at gmail dot com>
- Cc: Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>, binutils at sourceware dot org
- Date: Wed, 30 Sep 2015 20:58:28 -0400
- Subject: Re: [PATCH] enable fdpic targets/emulations for sh*-*-linux*
- Authentication-results: sourceware.org; auth=none
- References: <20150929235801 dot GA8408 at brightrain dot aerifal dot cx> <20150930 dot 143924 dot 179845457 dot kkojima at rr dot iij4u dot or dot jp> <20151001004107 dot GH32709 at bubble dot grove dot modra dot org>
On Thu, Oct 01, 2015 at 10:11:07AM +0930, Alan Modra wrote:
> On Wed, Sep 30, 2015 at 02:39:24PM +0900, Kaz Kojima wrote:
> > Rich Felker <dalias@libc.org> wrote:
> > > Currently sh/fdpic support in binutils is only enabled for
> > > sh{1,2,}-*-uclinux*. This patch adds it to the sh*-*-linux* targets
> > > which are what I'm using for musl's j2/sh2 support. sh2eb-*-linux-musl
> > > toolchains treat the target as regular Linux (modulo no fork and
> > > resticted mmap), produce binaries which are forward-compatible with
> > > sh3/4 Linux, and do not use any of the legacy flat binary stuff
> > > associated with *-uclinux* tuples, so it makes sense to use a *-linux*
> > > tuple.
> >
> > The patch is OK. I've committed it as two separated patches
> > which have independent ChangeLog entries below, because bfd
> > and ld have their own ChangeLog files. Thanks!
> >
> > Regards,
> > kaz
> > --
> > [bfd]
> > 2015-09-30 Rich Felker <dalias@libc.org>
> >
> > * config.bfd (targ_selvecs): Add fdpic and misc targets
> > for sh*-*-linux*.
> >
> > [ld]
> > 2015-09-30 Rich Felker <dalias@libc.org>
> >
> > * configure.tgt (targ_extra_emuls): Add fdpic and misc
> > emulations to sh*-*-linux* targets.
>
> This patch results in an enormous number of testsuite failures when
> building an x86_64-linux to sh-linux cross. Here is an example:
>
> ..../nm-new: tmpdir/bintest.o: File format is ambiguous
> ..../nm-new: Matching formats: elf32-sh-linux elf32-shl
Sorry about that. Do we need to just drop elf32-sh and elf32-shl?
They're not necessary for anything I'm using at the moment, and
probably not at all; I had just added them for completeness.
Rich