public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/464] New: IA64 math functions aren't weak
Date: Thu, 21 Oct 2004 18:03:00 -0000	[thread overview]
Message-ID: <20041021180347.464.hjl@lucon.org> (raw)

There are

[hjl@gnu-20 hjl]$ readelf -s /usr/lib/libm.a | grep " coshf"
     5: 00000000   145 FUNC    WEAK   DEFAULT    1 coshf

on ia32 and x86_64, but

[hjl@gnu-2 kernel]$ readelf -s /usr/lib/libm.a | grep " coshf"
    13: 0000000000000000  1616 FUNC    GLOBAL DEFAULT    1 coshf

on ia64. As the result, people can't override math functions in libm.a on
ia64 since other internal math functions in libm.a, like __ieee754_coshf,
are needed by glibc, which leads to symbol multiple definition error.

-- 
           Summary: IA64 math functions aren't weak
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: critical
          Priority: P2
         Component: math
        AssignedTo: aj at suse dot de
        ReportedBy: hjl at lucon dot org
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: ia64-unknown-linux-gnu
  GCC host triplet: ia64-unknown-linux-gnu
GCC target triplet: ia64-unknown-linux-gnu


http://sources.redhat.com/bugzilla/show_bug.cgi?id=464

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2004-10-21 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 18:03 hjl at lucon dot org [this message]
2004-10-26 20:37 ` [Bug math/464] " hjl at lucon dot org
2004-11-30 11:09 ` schwab@suse.de
2005-01-06 11:34 ` drepper at redhat dot com
2005-01-07  6:38 ` aj at suse dot de

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=20041021180347.464.hjl@lucon.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@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).