From: Steven Munroe <munroesj@us.ibm.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Problems with overriding FPU code from add-ons
Date: Thu, 16 Mar 2006 20:29:00 -0000 [thread overview]
Message-ID: <4419D7E2.80700@us.ibm.com> (raw)
Originally reported this to libc-ports, but now I am convinved this is a
general problem.
The directory search sequence does not allow add-ons to override ./fpu
code. In my case the (power4++) implementations of llrint.S and
llrintf.S from powerpc-cpu/sysdeps/powerpc/powerpc32/powerpc64/fpu/
are not overriding the implementations from
libc/sysdeps/powerpc/powerpc32/fpu.
From config.make we see:
config-sysdirs =
sysdeps/powerpc/powerpc32/elf
sysdeps/powerpc/elf
sysdeps/unix/sysv/linux/powerpc/powerpc32/fpu <<1>>
sysdeps/powerpc/powerpc32/fpu <<2>>
nptl/sysdeps/unix/sysv/linux/powerpc/powerpc32
sysdeps/unix/sysv/linux/powerpc/powerpc32
nptl/sysdeps/unix/sysv/linux/powerpc
sysdeps/unix/sysv/linux/powerpc
sysdeps/ieee754/ldbl-128ibm
sysdeps/ieee754/ldbl-opt
nptl/sysdeps/unix/sysv/linux
nptl/sysdeps/pthread
sysdeps/pthread
sysdeps/unix/sysv/linux
sysdeps/gnu
sysdeps/unix/common
sysdeps/unix/mman
sysdeps/unix/inet
nptl/sysdeps/unix/sysv
sysdeps/unix/sysv
sysdeps/unix/powerpc
nptl/sysdeps/unix
sysdeps/unix
sysdeps/posix
powerpc-cpu/sysdeps/powerpc/powerpc32/power4/fpu <<3>>
powerpc-cpu/sysdeps/powerpc/powerpc32/powerpc64/fpu <<4>>
powerpc-cpu/sysdeps/powerpc/powerpc32/power4
powerpc-cpu/sysdeps/powerpc/powerpc32
sysdeps/powerpc/powerpc32
sysdeps/wordsize-32
sysdeps/powerpc/fpu <<5>>
powerpc-cpu/sysdeps/powerpc
nptl/sysdeps/powerpc sysdeps/powerpc
sysdeps/ieee754/dbl-64
sysdeps/ieee754/flt-32
sysdeps/ieee754
powerpc-cpu/sysdeps/powerpc/powerpc32/powerpc64
sysdeps/generic/elf
sysdeps/generic
The <<#>> annotations are mine.
All the directories (including add-ons) in the list but the ./fpu
directorys from the libc (<<1>>, <<2>>) preceed the ./fpu directories
from ANY add-on (in my case <<3>> and <<4>>). This incorrect because
there there is no way for an add-on to override the ./libc
implementation for ./fpu directory.
reply other threads:[~2006-03-16 20:29 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=4419D7E2.80700@us.ibm.com \
--to=munroesj@us.ibm.com \
--cc=libc-hacker@sources.redhat.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).