From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Mark Salter <msalter@redhat.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Aurelien Jacquiot <a-jacquiot@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: c6x linker issue on linux-next-20160808 + some linker table work
Date: Tue, 9 Aug 2016 20:40:23 +0200 [thread overview]
Message-ID: <20160809184023.GD3296@wotan.suse.de> (raw)
In-Reply-To: <1470762240.3551.42.camel@redhat.com>
On Tue, Aug 09, 2016 at 01:04:00PM -0400, Mark Salter wrote:
> On Tue, 2016-08-09 at 06:37 -0700, Guenter Roeck wrote:
> > On 08/09/2016 01:11 AM, Luis R. Rodriguez wrote:
> > >
> > > Mark, Aurelien,
> > >
> > > I've run into a linker (ld) issue caused by the linker table work I've
> > > been working on [0]. I looked into this and for the life of me, I
> > > cannot comprehend what the problem is, so was hoping you folks might
> > > be able to chime in.
> > >
> > For reference, the error is
> >
> > c6x-elf-ld: drivers/built-in.o: SB-relative relocation but __c6xabi_DSBT_BASE not defined
> > c6x-elf-ld: drivers/built-in.o: SB-relative relocation but __c6xabi_DSBT_BASE not defined
>
> DSBT is a reference to the no-MMU userspace ABI used by c6x. The kernel shouldn't
> be referencing DSBT base. The -mno-dsbt gcc flag should prevent it.
I see -mno-dsbt on arch/c6x/Makefile already -- however at link time this is
an issue if linker tables are used it seems. Do you have any other recommendation?
I will note that it would seem that even i386 and x86-64 compiler/binutils seem
to have relocation issues on older compiler/binutils, for instance:
gcc-4.7.2
binutils-2.22
Yields:
x86_64:allyesconfig || x86_64:allmodconfig
Invalid absolute R_X86_64_64 relocation: __per_cpu_load
i386:defconfig
Invalid absolute R_386_32 relocation: __vvar_page
This issue on x86 is not observed as so far as of gcc 5.2.1
and binutils-2.26.1.
hpa -- if you can think of a work around for this for older compilers/linkers
let me know... unless we are OK to increase the requirements for x86.
Luis
next prev parent reply other threads:[~2016-08-09 18:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 8:11 c6x linker issue on linux-next-20160808 + some linker table work Luis R. Rodriguez
2016-08-09 13:37 ` Guenter Roeck
2016-08-09 17:04 ` Mark Salter
2016-08-09 18:40 ` Luis R. Rodriguez [this message]
2016-08-09 18:45 ` Mark Salter
2016-08-09 18:45 ` Mark Salter
2016-08-10 1:50 ` Mark Salter
[not found] ` <CAB=NE6XbxvpdsXecPLbh9krsKRvwKcwEzcve4XorpPetU3Xk6Q@mail.gmail.com>
2016-08-10 3:04 ` Mark Salter
2016-08-10 21:30 ` Luis R. Rodriguez
2016-08-10 21:30 ` Luis R. Rodriguez
2016-08-10 23:04 ` Mark Salter
2016-08-11 5:56 ` Luis R. Rodriguez
2016-08-11 11:32 ` Mark Salter
2016-08-11 15:59 ` Luis R. Rodriguez
2016-08-11 17:14 ` Mark Salter
2016-08-11 17:14 ` Mark Salter
2016-08-11 17:56 ` Luis R. Rodriguez
2016-08-11 17:56 ` Luis R. Rodriguez
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=20160809184023.GD3296@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=a-jacquiot@ti.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=msalter@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).