From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] insane: detect and warn about relocations in .text
Date: Wed, 3 Oct 2012 10:56:36 -0500 [thread overview]
Message-ID: <506C6034.6060707@windriver.com> (raw)
In-Reply-To: <1349278932.32611.140.camel@phil-desktop>
As an FYI -- if you have text relocations, then the prelinker will skip that
binary, resulting in lower startup performance. So as a general QA check, it's
well worth having.
--Mark
On 10/3/12 10:42 AM, Phil Blundell wrote:
> On Wed, 2012-10-03 at 11:24 +0100, Phil Blundell wrote:
>> Signed-off-by: Phil Blundell <pb@pbcl.net>
>> ---
>> This requires qa.elf.run_objdump() so needs to be applied after the
>> patch which adds that function.
>
> By the way, the background motivation for this was that the current
> oe-core version of gcc seems to be somewhat broken in this respect on
> MIPS; it seems to have reverted to generating an .eh_frame with a
> relocation in it which results in DT_TEXTREL on the binary.
>
> With -fasynchronous-unwind-tables it seems to get even worse. I don't
> quite recall exactly what the failure was there but it was bad enough to
> make it unusable.
>
> I think both of these problems are regressions from the gcc-4.6 that we
> were using previously. I'm not quite sure at what point it went wrong
> though.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-10-03 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 15:42 [PATCH] insane: detect and warn about relocations in .text Phil Blundell
2012-10-03 15:56 ` Mark Hatle [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-06 17:24 Phil Blundell
2012-11-07 9:59 ` Mark Hatle
2012-11-07 14:37 ` Richard Purdie
2012-10-03 10:24 Phil Blundell
2012-10-03 10:31 ` Martin Jansa
2012-10-03 10:44 ` Phil Blundell
2012-10-03 11:19 ` Richard Purdie
2012-10-03 12:39 ` Phil Blundell
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=506C6034.6060707@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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