public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug ports/15632] New: MIPS sqrt implementations not being used
Date: Fri, 14 Jun 2013 21:06:00 -0000 [thread overview]
Message-ID: <bug-15632-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15632
Bug ID: 15632
Summary: MIPS sqrt implementations not being used
Product: glibc
Version: 2.17
Status: NEW
Severity: normal
Priority: P2
Component: ports
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
CC: carlos at redhat dot com, roland at gnu dot org
Host: mips*-linux*
The sysdeps directory ordering for mips*-linux* is such that the MIPS sqrt
implementations in ports/sysdeps/mips/fpu/ don't get used because the flt-32
and dbl-64 directories come first. For n32 I see:
ports/sysdeps/unix/sysv/linux/mips/mips64/n32/nptl
ports/sysdeps/unix/sysv/linux/mips/mips64/n32
ports/sysdeps/unix/sysv/linux/mips/mips64/nptl
ports/sysdeps/unix/sysv/linux/mips/mips64
ports/sysdeps/unix/sysv/linux/mips/nptl ports/sysdeps/unix/sysv/linux/mips
nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread
ports/sysdeps/unix/sysv/linux sysdeps/unix/sysv/linux sysdeps/gnu
sysdeps/unix/inet nptl/sysdeps/unix/sysv ports/sysdeps/unix/sysv
sysdeps/unix/sysv ports/sysdeps/unix/mips/mips64/n32
ports/sysdeps/unix/mips/mips64 ports/sysdeps/unix/mips nptl/sysdeps/unix
ports/sysdeps/unix sysdeps/unix sysdeps/posix ports/sysdeps/mips/mips64/n32
ports/sysdeps/mips/ieee754 sysdeps/ieee754/ldbl-128
ports/sysdeps/mips/mips64/soft-fp ports/sysdeps/mips/mips64
sysdeps/ieee754/flt-32 sysdeps/ieee754/dbl-64 ports/sysdeps/mips
sysdeps/wordsize-32 ports/sysdeps/mips/fpu ports/sysdeps/mips/nptl
sysdeps/ieee754 sysdeps/generic
For o32 I see:
ports/sysdeps/unix/sysv/linux/mips/mips32/nptl
ports/sysdeps/unix/sysv/linux/mips/mips32
ports/sysdeps/unix/sysv/linux/mips/nptl ports/sysdeps/unix/sysv/linux/mips
nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread
ports/sysdeps/unix/sysv/linux sysdeps/unix/sysv/linux sysdeps/gnu
sysdeps/unix/inet nptl/sysdeps/unix/sysv ports/sysdeps/unix/sysv
sysdeps/unix/sysv ports/sysdeps/unix/mips/mips32 ports/sysdeps/unix/mips
nptl/sysdeps/unix ports/sysdeps/unix sysdeps/unix sysdeps/posix
ports/sysdeps/mips/mips32/fpu ports/sysdeps/mips/mips32
ports/sysdeps/mips/ieee754 ports/sysdeps/mips sysdeps/ieee754/flt-32
sysdeps/ieee754/dbl-64 sysdeps/wordsize-32 ports/sysdeps/mips/fpu
ports/sysdeps/mips/nptl sysdeps/ieee754 sysdeps/generic
For n64 I see:
ports/sysdeps/unix/sysv/linux/mips/mips64/n64/nptl
ports/sysdeps/unix/sysv/linux/mips/mips64/n64
ports/sysdeps/unix/sysv/linux/mips/mips64/nptl
ports/sysdeps/unix/sysv/linux/mips/mips64
ports/sysdeps/unix/sysv/linux/mips/nptl ports/sysdeps/unix/sysv/linux/mips
nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread
ports/sysdeps/unix/sysv/linux sysdeps/unix/sysv/linux sysdeps/gnu
sysdeps/unix/inet nptl/sysdeps/unix/sysv ports/sysdeps/unix/sysv
sysdeps/unix/sysv ports/sysdeps/unix/mips/mips64/n64
ports/sysdeps/unix/mips/mips64 ports/sysdeps/unix/mips nptl/sysdeps/unix
ports/sysdeps/unix sysdeps/unix sysdeps/posix ports/sysdeps/mips/mips64/n64
ports/sysdeps/mips/ieee754 sysdeps/ieee754/ldbl-128
ports/sysdeps/mips/mips64/soft-fp ports/sysdeps/mips/mips64
sysdeps/ieee754/flt-32 sysdeps/ieee754/dbl-64 ports/sysdeps/mips
sysdeps/wordsize-64 ports/sysdeps/mips/fpu ports/sysdeps/mips/nptl
sysdeps/ieee754 sysdeps/generic
The simple fix probably is wrapping these files in more specific directories
such as mips/mips32/fpu that come early enough in the sysdeps ordering; I don't
know if there's a better approach.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-06-14 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 21:06 jsm28 at gcc dot gnu.org [this message]
2013-10-03 20:07 ` [Bug ports/15632] " sje at gcc dot gnu.org
2014-06-13 15:04 ` 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-15632-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).