From: "Joseph S. Myers" <joseph@codesourcery.com>
To: libc-ports@sourceware.org
Subject: powerpc-nofpu: Allow abort and soft-fp symbols to be absent in localplt test
Date: Wed, 13 Jun 2012 21:15:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1206132112280.29380@digraph.polyomino.org.uk> (raw)
I've applied this patch to fix check-localplt for powerpc-nofpu. The
problem I observed was the entry for abort being absent; since that
symbol's presence (from calls in soft-fp that may or may not be optimized
away), and that of symbols from soft-fp, has previously been known to
depend on compiler versions, I marked all the relevant symbols with '?' to
make them optional in the localplt data.
diff --git a/ChangeLog.powerpc b/ChangeLog.powerpc
index 8ad5bad..0c7d3af 100644
--- a/ChangeLog.powerpc
+++ b/ChangeLog.powerpc
@@ -1,3 +1,8 @@
+2012-06-13 Joseph Myers <joseph@codesourcery.com>
+
+ * data/localplt-powerpcsoft-linux-gnu.data: Allow abort and
+ soft-fp symbols to be absent.
+
2012-06-08 Joseph Myers <joseph@codesourcery.com>
* sysdeps/unix/sysv/linux/powerpc/powerpc32/nofpu/nptl/libc.abilist:
diff --git a/data/localplt-powerpcsoft-linux-gnu.data b/data/localplt-powerpcsoft-linux-gnu.data
index 65fa5da..0743b08 100644
--- a/data/localplt-powerpcsoft-linux-gnu.data
+++ b/data/localplt-powerpcsoft-linux-gnu.data
@@ -1,32 +1,32 @@
libc.so: _Unwind_Find_FDE
-libc.so: __adddf3
-libc.so: __addsf3
-libc.so: __divdf3
-libc.so: __divsf3
-libc.so: __eqdf2
-libc.so: __eqsf2
-libc.so: __extendsfdf2
-libc.so: __fixdfsi
-libc.so: __fixsfsi
-libc.so: __fixunsdfsi
-libc.so: __floatsidf
-libc.so: __floatsisf
-libc.so: __floatunsidf
-libc.so: __floatunsisf
-libc.so: __gedf2
-libc.so: __gtdf2
-libc.so: __ledf2
-libc.so: __ltdf2
-libc.so: __muldf3
-libc.so: __mulsf3
-libc.so: __nedf2
+libc.so: __adddf3 ?
+libc.so: __addsf3 ?
+libc.so: __divdf3 ?
+libc.so: __divsf3 ?
+libc.so: __eqdf2 ?
+libc.so: __eqsf2 ?
+libc.so: __extendsfdf2 ?
+libc.so: __fixdfsi ?
+libc.so: __fixsfsi ?
+libc.so: __fixunsdfsi ?
+libc.so: __floatsidf ?
+libc.so: __floatsisf ?
+libc.so: __floatunsidf ?
+libc.so: __floatunsisf ?
+libc.so: __gedf2 ?
+libc.so: __gtdf2 ?
+libc.so: __ledf2 ?
+libc.so: __ltdf2 ?
+libc.so: __muldf3 ?
+libc.so: __mulsf3 ?
+libc.so: __nedf2 ?
libc.so: __signbit
libc.so: __signbitl
-libc.so: __subdf3
-libc.so: __subsf3
-libc.so: __truncdfsf2
-libc.so: __unorddf2
-libc.so: abort
+libc.so: __subdf3 ?
+libc.so: __subsf3 ?
+libc.so: __truncdfsf2 ?
+libc.so: __unorddf2 ?
+libc.so: abort ?
libc.so: calloc
libc.so: free
libc.so: malloc
--
Joseph S. Myers
joseph@codesourcery.com
reply other threads:[~2012-06-13 21:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.1206132112280.29380@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@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).