From: Mark Hatle <mark.hatle@windriver.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc: Fix for dynamic linker broken offset
Date: Fri, 28 Sep 2012 10:02:45 -0500 [thread overview]
Message-ID: <5065BC15.4040608@windriver.com> (raw)
In-Reply-To: <1348844247.32611.54.camel@phil-desktop>
On 9/28/12 9:57 AM, Phil Blundell wrote:
> On Fri, 2012-09-28 at 09:35 -0500, Mark Hatle wrote:
>> On 9/28/12 9:02 AM, Phil Blundell wrote:
>>> On Fri, 2012-09-28 at 08:57 -0500, Mark Hatle wrote:
>>>> On 9/28/12 4:52 AM, Phil Blundell wrote:
>>>>> On Mon, 2012-09-24 at 15:40 +0300, Andrei Dinu wrote:
>>>>>> On 09/24/2012 02:30 PM, Phil Blundell wrote:
>>>>>>> On Mon, 2012-09-24 at 14:26 +0300, Andrei Dinu wrote:
>>>>>>>> +- *reloc_addr += sym->st_value;
>>>>>>>> ++ *reloc_addr = sym->st_value;
>>>>>>> That patch looks slightly dubious to me. Are you sure this doesn't
>>>>>>> introduce any regressions elsewhere?
>>>>>>>
>>>>>> I have insufficient data to affirm that it doesn't introduces regressions.
>>>>>
>>>>> Presumably it does at least pass the eglibc and binutils testsuites,
>>>>> right?
>>>>
>>>> That patch is a workaround for an ARM issue related to thread local storage and
>>>> TLS offsets during runtime and prelinking.
>>>
>>> Right, I understand that. But this doesn't really answer the question
>>> "does the workaround break anything else?".
>>
>> In my testing no. But I never integrated it with OE, so I never ran the test
>> suite Khem was referring to.
>
> I think the testsuite Khem mentioned is just eglibc's builtin tests; it
> isn't actually specific to OE. What did your testing consist of?
>
We have a battery of application tests which more or less consist of running all
of the binaries on the system and looking for minimal reasonable behavior for
each. (Other apps get more exhaustive testing of course.)
Also the reported case of libust/librcu was verified as well.
I'm not sure if it was run, but typically we also run the LTP test suite and LSB
test suite.. (but I didn't personally use it.)
--Mark
> p.
>
>
next prev parent reply other threads:[~2012-09-28 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:26 [PATCH] eglibc: Fix for dynamic linker broken offset Andrei Dinu
2012-09-24 11:30 ` Phil Blundell
2012-09-24 12:40 ` Andrei Dinu
2012-09-28 9:52 ` Phil Blundell
2012-09-28 13:57 ` Mark Hatle
2012-09-28 14:00 ` Khem Raj
2012-09-28 14:02 ` Phil Blundell
2012-09-28 14:35 ` Mark Hatle
2012-09-28 14:50 ` Khem Raj
2012-09-28 14:57 ` Phil Blundell
2012-09-28 15:02 ` Mark Hatle [this message]
[not found] ` <50659938.4060401@intel.com>
2012-10-02 16:50 ` Phil Blundell
2012-09-24 14:34 ` Saul Wold
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=5065BC15.4040608@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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