public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/29810] ld: (Warning) Unsatisfied symbol "fmodl" in file /mnt/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs/libgfortran.sl
Date: Sun, 12 Nov 2006 19:38:00 -0000 [thread overview]
Message-ID: <20061112193823.18217.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29810-276@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2006-11-12 19:38 -------
Subject: Re: ld: (Warning) Unsatisfied symbol "fmodl" in file
/mnt/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.l
> ------- Comment #2 from kargl at gcc dot gnu dot org 2006-11-12 16:22 -------
> Just curious. Do you file bug reports with HP about the
> lack of C99 long double libm functions?
I don't have a service contract that allows for filing bug reports
with HP.
There's no hope for hpux <= 11.23. Don't know if HP will complete
C99 support in 11.31.
Although the PA-RISC architecture provides for long double support
in hardware, this has not been implemented. So, I wonder if HP will
bother with the C99 long double libm functions. The long double
emulation code that's present in hpux caused various issues with
Ada, so we don't use it anymore.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29810
next prev parent reply other threads:[~2006-11-12 19:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 15:54 [Bug libfortran/29810] New: " danglin at gcc dot gnu dot org
2006-11-12 16:11 ` [Bug libfortran/29810] " danglin at gcc dot gnu dot org
2006-11-12 16:22 ` kargl at gcc dot gnu dot org
2006-11-12 16:36 ` kargl at gcc dot gnu dot org
2006-11-12 19:38 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2006-11-13 2:40 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-21 0:05 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-21 2:05 ` kargl at gcc dot gnu dot org
2006-11-21 2:26 ` dave at hiauly1 dot hia dot nrc dot ca
2006-12-02 8:20 ` [Bug libfortran/29810] Unsatisfied symbol "fmodl" in libgfortran shared library ebotcazou at gcc dot gnu dot org
2006-12-02 8:21 ` [Bug libfortran/29810] [4.1/4.2/4.3 regression] " ebotcazou at gcc dot gnu dot org
2006-12-02 8:27 ` ebotcazou at gcc dot gnu dot org
2006-12-02 8:30 ` pinskia at gcc dot gnu dot org
2006-12-02 16:51 ` dave at hiauly1 dot hia dot nrc dot ca
2006-12-03 11:39 ` fxcoudert at gcc dot gnu dot org
2006-12-03 16:14 ` fxcoudert at gcc dot gnu dot org
2006-12-03 22:03 ` ebotcazou at gcc dot gnu dot org
2006-12-03 22:04 ` ebotcazou at gcc dot gnu dot org
2006-12-04 9:10 ` pault at gcc dot gnu dot org
2006-12-04 9:22 ` ebotcazou at gcc dot gnu dot org
2006-12-04 16:44 ` sgk at troutmask dot apl dot washington dot edu
2006-12-04 16:47 ` sgk at troutmask dot apl dot washington dot edu
2006-12-04 17:06 ` ebotcazou at gcc dot gnu dot org
2006-12-04 17:40 ` sgk at troutmask dot apl dot washington dot edu
2006-12-04 20:54 ` ebotcazou at gcc dot gnu dot org
2006-12-04 21:13 ` dave at hiauly1 dot hia dot nrc dot ca
2006-12-04 21:37 ` sgk at troutmask dot apl dot washington dot edu
2006-12-04 22:18 ` ebotcazou at gcc dot gnu dot org
2006-12-04 22:52 ` dave at hiauly1 dot hia dot nrc dot ca
2006-12-06 10:04 ` fxcoudert at gcc dot gnu dot org
2006-12-06 10:56 ` fxcoudert at gcc dot gnu dot org
2006-12-06 13:13 ` ebotcazou at gcc dot gnu dot org
2006-12-06 21:18 ` fxcoudert at gcc dot gnu dot org
2006-12-06 21:50 ` fxcoudert at gcc dot gnu dot org
2006-12-06 21:51 ` fxcoudert at gcc dot gnu dot org
2006-12-06 22:04 ` dave at hiauly1 dot hia dot nrc dot ca
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=20061112193823.18217.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).