public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/15687] New: powerpc64 abi breakage with nocancel functions
Date: Thu, 27 Jun 2013 01:17:00 -0000 [thread overview]
Message-ID: <bug-15687-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15687
Bug ID: 15687
Summary: powerpc64 abi breakage with nocancel functions
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: nptl
Assignee: unassigned at sourceware dot org
Reporter: amodra at gmail dot com
CC: drepper.fsp at gmail dot com
glibc contains powerpc64 functions without functions descriptors. As seen in
nptl/ptw-pause.o
[snip]
[ 1] .text PROGBITS 0000000000000000 000040 0000b4 00 AX 0 0 4
[snip]
[ 5] .opd PROGBITS 0000000000000000 0000f8 000018 00 WA 0 0 8
[snip]
10: 0000000000000000 180 FUNC GLOBAL DEFAULT 5 __libc_pause
11: 000000000000000c 48 FUNC GLOBAL DEFAULT 1 __pause_nocancel
Notice that __pause_nocancel is define in .text, ie. does not have a function
descriptor. This triggered an error in powerpc64 gold --gc-sections.
It looks to me like
nptl/sysdeps/unix/sysv/linux/powerpc/powerpc64/sysdep-cancel.h is the culprit.
The ENTRY macro normally is reposible for generating function descriptors, but
I see no such thing for the nocancel variant entry point.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-06-27 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 1:17 amodra at gmail dot com [this message]
2013-06-27 12:40 ` [Bug nptl/15687] " schwab@linux-m68k.org
2013-06-27 15:22 ` amodra at gmail dot com
2013-06-27 16:02 ` schwab@linux-m68k.org
2013-07-17 18:38 ` jingyuuiuc at gmail dot com
2013-07-17 20:48 ` schwab@linux-m68k.org
2013-08-11 2:49 ` amodra at gmail dot com
2014-06-13 13:30 ` 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-15687-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).