public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/15905] New: [ARM] IFUNC support broken for REL relocs.
@ 2013-08-29  3:46 carlos at redhat dot com
  2013-08-29  3:46 ` [Bug libc/15905] " carlos at redhat dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: carlos at redhat dot com @ 2013-08-29  3:46 UTC (permalink / raw)
  To: glibc-bugs

http://sourceware.org/bugzilla/show_bug.cgi?id=15905

            Bug ID: 15905
           Summary: [ARM] IFUNC support broken for REL relocs.
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: carlos at redhat dot com
                CC: drepper.fsp at gmail dot com

On ARM in dl-machine.h (elf_machine_rel) when handling R_ARM_IRELATIVE
relocations for STT_GNU_IFUNC we fail to pass dl_hwcap to the IFUNC resolver
resulting in the wrong function being selected for the current hardware.

When building glibc with multi-arch support and the VFP ABI this will cause the
NEON variants of functions to be selected even though NEON hardware might not
be present.

On hardware without NEON support the built glibc will fail to run correctly.
This is immediately obvious as most of the testsuite will fail with SIGILL on
this hardware.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-06-13 12:58 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-29  3:46 [Bug libc/15905] New: [ARM] IFUNC support broken for REL relocs carlos at redhat dot com
2013-08-29  3:46 ` [Bug libc/15905] " carlos at redhat dot com
2013-08-29  4:02 ` carlos at redhat dot com
2013-08-29  4:24 ` carlos at redhat dot com
2014-06-13 12:58 ` fweimer at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).