From: "Hong, Brandon" <brandon.hong@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] Fix global symbol loading failure in resolve function
Date: Tue, 24 Sep 2019 14:22:02 +0000 [thread overview]
Message-ID: <AB142004-E740-4450-807D-5ADEA95D565B@intel.com> (raw)
In-Reply-To: <156931357819.29243.12854292800894160440@skylake-alporthouse-com>
Unfortunately, I do not have a clear answer why it's not bound.
I guess it's related to IFUNC lazy binding because I observed crash call stack related to glibc elf_machine_rela() and the crash didn’t happen when I call the same global function igt_x86_features() in rewritten generic FUNC igt_half_to_float() for testing.
- Brandon
> On 24 Sep 2019, at 5:26 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> Quoting brandon.hong@intel.com (2019-09-24 09:02:07)
>> From: Brandon Hong <brandon.hong@intel.com>
>>
>> 270 out of 284 tests get failed with SIGSEGV on ClearLinux because the ifunc
>> resolver resolve_half_to_float() tries to call unbound global function
>> igt_x86_features(). This patch fixes the issue by adding a F16C checking
>> local function.
>
> So, out of curiosity, why is the global function not bound?
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-09-24 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 8:02 [igt-dev] [PATCH i-g-t] Fix global symbol loading failure in resolve function brandon.hong
2019-09-24 8:26 ` Chris Wilson
2019-09-24 14:22 ` Hong, Brandon [this message]
2019-09-24 8:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2019-09-24 8:55 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-09-24 17:28 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-09-24 14:02 [igt-dev] [PATCH i-g-t] " brandon.hong
2019-09-27 17:26 ` Ville Syrjälä
2019-09-30 9:04 ` Hong, Brandon
2019-09-30 9:06 brandon.hong
2019-09-30 9:30 brandon.hong
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=AB142004-E740-4450-807D-5ADEA95D565B@intel.com \
--to=brandon.hong@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.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