From: Mark Salter <msalter@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Aurelien Jacquiot <a-jacquiot@ti.com>
Cc: "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, 09 Aug 2016 13:04:00 -0400 [thread overview]
Message-ID: <1470762240.3551.42.camel@redhat.com> (raw)
In-Reply-To: <741c0f4d-bd9c-f28a-12d1-64bb483c6998@roeck-us.net>
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.
>
> Toolchain used is:
>
> c6x-elf-gcc (GCC) 5.2.0
> GNU ld (GNU Binutils) 2.25
>
> Guenter
>
> >
> > A snapshot you can use is available here:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux-next.git/log/?h=20160808-linker-table-v4
> >
> > The commit that causes the issue is "firmware: port built-in section
> > to linker table":
> >
> > https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux-next.git/commit/?h=20160808-linker-table-v4&id=2f4516be8c89b3ca008962798d44b54751e62844
> >
> > its the first use of linker tables in the kernel, but I can't figure
> > out why this error comes up, nor how to fix it. Any ideas?
> >
> > [0] lkml.kernel.org/r/1469222687-1600-1-git-send-email-mcgrof@kernel.org
> >
> > Luis
> >
next prev parent reply other threads:[~2016-08-09 17:04 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 [this message]
2016-08-09 18:40 ` Luis R. Rodriguez
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=1470762240.3551.42.camel@redhat.com \
--to=msalter@redhat.com \
--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=mcgrof@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 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).