From: "Joseph S. Myers" <joseph@codesourcery.com>
To: libc-ports@sourceware.org
Cc: "Ryan S. Arnold" <ryan.arnold@gmail.com>
Subject: powerpc-nofpu ABI baselines
Date: Wed, 16 May 2012 21:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205162119220.32674@digraph.polyomino.org.uk> (raw)
I've added ABI baselines for powerpc-nofpu in
sysdeps/unix/sysv/linux/powerpc/powerpc32/nofpu/nptl/. Rather than
sending the large files here, instead here's the diff against the
baselines for powerpc32-fpu. I think the changes here are correct - that
is, the symbols really were in the relevant versions (although I only did
some spot checks against 2.5 binaries, not 2.3/2.4), and at least as of
2.5 it really does seem to be the case that powerpc-nofpu glibc does not
export the __longjmp symbol at all, so the removal of that symbol
(relative to the fpu version) seems right.
This only has the changes that seem clearly right. I'll send a separate
message about the trickier parts of the ABI baseline.
diff -ruN nptl-fpu/libc.abilist nptl/libc.abilist
--- nptl-fpu/libc.abilist 2012-05-16 12:42:09.552250925 -0700
+++ nptl/libc.abilist 2012-05-16 14:00:26.162292503 -0700
@@ -2065,7 +2089,36 @@
wctype_l F
GLIBC_2.3.2
GLIBC_2.3.2 A
+ __adddf3 F
+ __addsf3 F
+ __divdf3 F
+ __divsf3 F
+ __eqdf2 F
+ __eqsf2 F
+ __extendsfdf2 F
+ __fixdfsi F
+ __fixsfsi F
+ __fixunsdfsi F
+ __fixunssfsi F
+ __floatsidf F
+ __floatsisf F
+ __gedf2 F
+ __gesf2 F
+ __ledf2 F
+ __lesf2 F
+ __muldf3 F
+ __mulsf3 F
+ __negdf2 F
+ __negsf2 F
__register_atfork F
+ __sim_disabled_exceptions D 0x4
+ __sim_exceptions D 0x4
+ __sim_round_mode D 0x4
+ __sqrtdf2 F
+ __sqrtsf2 F
+ __subdf3 F
+ __subsf3 F
+ __truncdfsf2 F
epoll_create F
epoll_ctl F
epoll_wait F
@@ -2108,7 +2161,6 @@
__chk_fail F
__fprintf_chk F
__gets_chk F
- __longjmp F
__memcpy_chk F
__memmove_chk F
__mempcpy_chk F
@@ -2161,6 +2213,10 @@
__fgetws_chk F
__fgetws_unlocked_chk F
__finitel F
+ __floatundidf F
+ __floatundisf F
+ __floatunsidf F
+ __floatunsisf F
__fprintf_chk F
__fwprintf_chk F
__fxstatat F
@@ -2171,11 +2227,17 @@
__gethostname_chk F
__getlogin_r_chk F
__getwd_chk F
+ __gtdf2 F
+ __gtsf2 F
__isinfl F
__isnanl F
+ __ltdf2 F
+ __ltsf2 F
__mbsnrtowcs_chk F
__mbsrtowcs_chk F
__mbstowcs_chk F
+ __nedf2 F
+ __nesf2 F
__nldbl__IO_fprintf F
__nldbl__IO_printf F
__nldbl__IO_sprintf F
@@ -2265,6 +2327,8 @@
__swprintf_chk F
__syslog_chk F
__ttyname_r_chk F
+ __unorddf2 F
+ __unordsf2 F
__vfprintf_chk F
__vfscanf F
__vfwprintf_chk F
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2012-05-16 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 21:23 Joseph S. Myers [this message]
2012-05-16 21:37 ` Joseph S. Myers
2012-05-16 21:42 ` Roland McGrath
2012-05-16 21:58 ` Joseph S. Myers
2012-05-16 22:03 ` Roland McGrath
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.1205162119220.32674@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=ryan.arnold@gmail.com \
/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).