public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8197: std::sin(float) causes undefined reference to sinf
Date: Sun, 27 Oct 2002 13:46:00 -0000	[thread overview]
Message-ID: <20021027214603.7790.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/8197; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
Cc: gcc-gnats@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: libstdc++/8197: std::sin(float) causes undefined reference to sinf
Date: 27 Oct 2002 23:41:47 +0100

 "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> writes:
 
 |  I got some more information on this one and a patch that fixes the
 |  problem for me:
 
 Thanks for reporting more info on this issue.
 
 [...]
 
 |  The problem seems to be that std::sin(float) is an inline function defined in
 |  cmath. This inline function uses __builtin_sinf which in turn generates
 |  a reference to a function sinf.
 |  This function even exists and is exported from stubs.o:
 |  
 |  turing# nm sparc-sun-solaris2.9/libstdc++-v3/libmath/stubs.o  |grep sinf
 |  00000714 T sinf
 |  
 |  However, in libstdc++.so the symbol sinf is private:
 
 Benjamin,
 
   Do we have infrastructure to export symbols based on target
 configurations?  If not, does telling linker-map.gnu to export
 non-existing symbols an error?  If not, is it documented to work as
 "expected"?
 
 Thanks,
 
 -- Gaby
 PS: I just realized I asked more questions that could provide any hints.


             reply	other threads:[~2002-10-27 21:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27 13:46 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05  8:10 bkoz
2002-11-04 17:16 B. Kosnik
2002-11-02  8:26 Christian Ehrhardt
2002-11-01  9:44 bkoz
2002-10-28 10:26 Benjamin Kosnik
2002-10-27 14:36 Phil Edwards
2002-10-26  6:46 Christian Ehrhardt
2002-10-11  7:26 ehrhardt

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=20021027214603.7790.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).