From: Uros Bizjak <ubizjak@gmail.com>
To: Fortran List <fortran@gcc.gnu.org>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
FX <fxcoudert@gmail.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: For testing: full __float128 patch
Date: Mon, 30 Aug 2010 01:55:00 -0000 [thread overview]
Message-ID: <1283114926.2376.4.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
Hello!
> On Sun, Aug 29, 2010 at 09:01:49AM +0200, FX wrote:
> > GCC >= 4.5 is needed. I'll add a check to libquad's configure.
> >
> > FX
> >
>
> Further testing on i386-*-freebsd runs into undefined symbols.
>
> libquad.so: undefined reference to `__getf2'
> libquad.so: undefined reference to `__eqtf2'
> libquad.so: undefined reference to `__addtf3'
> libquad.so: undefined reference to `__floatsitf'
> libquad.so: undefined reference to `__trunctfxf2'
> libquad.so: undefined reference to `__divtf3'
> libquad.so: undefined reference to `__letf2'
> libquad.so: undefined reference to `__unordtf2'
> libquad.so: undefined reference to `__fixtfdi'
> libquad.so: undefined reference to `__fixtfsi'
> libquad.so: undefined reference to `__lttf2'
> libquad.so: undefined reference to `__netf2'
> libquad.so: undefined reference to `__extendxftf2'
> libquad.so: undefined reference to `__extenddftf2'
> libquad.so: undefined reference to `__multf3'
> libquad.so: undefined reference to `__gttf2'
> libquad.so: undefined reference to `__subtf3'
> libgfortran.so: undefined reference to `__floatunditf'
> libquad.so: undefined reference to `__trunctfdf2'
>
>
> AFAICT, these should come from libgcc_s.so.1, but for whatever
> reason these are missing. I have been unable to find how
> to induce gcc to build the required files.
Try to build gcc with attached patch...
Uros.
[-- Attachment #2: c.diff.txt --]
[-- Type: text/plain, Size: 523 bytes --]
Index: config.gcc
===================================================================
--- config.gcc (revision 163630)
+++ config.gcc (working copy)
@@ -3485,6 +3485,9 @@
i[34567]86-*-cygwin* | i[34567]86-*-mingw* | x86_64-*-mingw*)
tmake_file="${tmake_file} i386/t-fprules-softfp soft-fp/t-softfp"
;;
+ i[34567]86-*-freebsd* | x86_64-*-freebsd*)
+ tmake_file="${tmake_file} i386/t-fprules-softfp soft-fp/t-softfp"
+ ;;
ia64*-*-linux*)
tmake_file="${tmake_file} ia64/t-fprules-softfp soft-fp/t-softfp"
;;
next reply other threads:[~2010-08-29 20:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 1:55 Uros Bizjak [this message]
2010-08-30 1:59 ` Steve Kargl
2010-08-30 7:42 ` Uros Bizjak
2010-08-30 10:46 ` Gerald Pfeifer
2010-08-30 16:48 ` Gerald Pfeifer
2010-08-30 17:34 ` Joseph S. Myers
2010-08-30 17:43 ` Uros Bizjak
2010-08-30 18:27 ` Richard Henderson
2010-08-30 19:25 ` Uros Bizjak
2010-08-30 19:38 ` Uros Bizjak
2010-08-30 19:51 ` Richard Henderson
2010-08-30 19:54 ` Jakub Jelinek
2010-08-30 22:29 ` Uros Bizjak
2010-08-31 4:32 ` Steve Kargl
2010-08-31 7:10 ` Steve Kargl
2010-08-31 3:37 ` Joseph S. Myers
2010-08-30 17:37 ` Steve Kargl
-- strict thread matches above, loose matches on Subject: below --
2010-08-29 0:57 FX
2010-08-29 1:48 ` Steve Kargl
2010-08-29 7:03 ` Steve Kargl
2010-08-29 11:43 ` Steve Kargl
2010-08-29 12:02 ` FX
2010-08-29 20:48 ` Steve Kargl
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=1283114926.2376.4.camel@localhost.localdomain \
--to=ubizjak@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).