From: "Frank Ch. Eigler" <fche@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: [Ltt-dev] Linux Kernel Markers : sparc build issue
Date: Wed, 07 Feb 2007 19:30:55 +0000 [thread overview]
Message-ID: <20070207193055.GC7196@redhat.com> (raw)
In-Reply-To: <20070207171912.GA5992@Krystal>
Hi -
> It seems like I bust the 8k limit for the sparc GOT :
> The kallsyms_addresses is 8614 lines long (for a 33.6kB total) in the .S,
> and, according to
> http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Code-Gen-Options.html :
> [...]
That could be it, but I don't see how that table of symbol addresses
.long _text - 0xbeef
is using any GOT slots at all. (Plus I don't know how a R_SPARC_32
could ever be truncated - maybe there is a 64- vs 32-bit toolchain
confusion happening somewhere?)
I could be misunderstanding things, but maybe what's wrong is that the
new markers section is located in a sensitive spot, and its size is
causing something else to no longer be reachable by shorter offsets.
What are the neighbouring regions in the linker script?
- FChE
next prev parent reply other threads:[~2007-02-07 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:19 [Ltt-dev] Linux Kernel Markers : sparc build issue Mathieu Desnoyers
2007-02-07 18:46 ` Mathieu Desnoyers
2007-02-07 19:30 ` Frank Ch. Eigler [this message]
2007-02-07 20:03 ` Mathieu Desnoyers
2007-02-07 20:21 ` Mathieu Desnoyers
2007-02-07 20:32 ` Mathieu Desnoyers
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=20070207193055.GC7196@redhat.com \
--to=fche@redhat.com \
--cc=sparclinux@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.