public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15905] New: [ARM] IFUNC support broken for REL relocs.
Date: Thu, 29 Aug 2013 03:46:00 -0000 [thread overview]
Message-ID: <bug-15905-131@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2013-08-29 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 3:46 carlos at redhat dot com [this message]
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
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=bug-15905-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).