Bug 1385089

Summary:	ltrace: implement ifunc support for aarch64.
Product:	Red Hat Developer Toolset	Reporter:	Martin Cermak <mcermak>
Component:	ltrace	Assignee:	DJ Delorie <dj>
Status:	CLOSED WONTFIX	QA Contact:	Martin Cermak <mcermak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	DTS 7.0 RHEL 7	CC:	codonell, dj, dsmith, jakub, kanderso, law, mcermak, mnewsome, mpolacek, nickc, nobody+bgollahe, palves, pfrankli, rzima
Target Milestone:	alpha
Target Release:	7.0
Hardware:	aarch64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1358371	Environment:
Last Closed:	2020-12-15 07:47:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.