Bug 1385089 - ltrace: implement ifunc support for aarch64.
Summary: ltrace: implement ifunc support for aarch64.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Developer Toolset
Classification: Red Hat
Component: ltrace
Version: DTS 7.0 RHEL 7
Hardware: aarch64
OS: Linux
medium
medium
Target Milestone: alpha
: 7.0
Assignee: DJ Delorie
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 17:09 UTC by Martin Cermak
Modified: 2020-12-15 07:47 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1358371
Environment:
Last Closed: 2020-12-15 07:47:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Martin Cermak 2016-10-14 17:09:34 UTC 
+++ This bug was initially created as a clone of Bug #1358371 +++

--- Additional comment from DJ Delorie on 2016-10-12 22:39:50 CEST ---

The aarch64 port does not yet have support for irelative symbols (nor upstream).  Normal symbols aren't effected, and the bug results in a symbol name of '' being printed for those symbols with default command line arguments.  So far, only ppc, s390, and x86 support irelative symbols.

Fixing aarch64 depends on (1) aarch64 itself supporting irelative symbols (looks like it), and a (2) a short arch-specific hook being added.  Note that this would be upstream work, not a backport.

--- Additional comment from Jeff Law on 2016-10-13 14:51:08 CEST ---

ifunc support for aarch64 isn't a priority.  We're not using ifuncs on aarch64 in RHEL yet.
Comment 1 Nick Clifton 2016-11-08 15:36:16 UTC 
Since this feature isn't even available in upstream FSF binutils sources I am resetting this BZ to DTS 7.0.
Comment 6 RHEL Program Management 2020-12-15 07:47:09 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.