public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Fortran List <fortran@gcc.gnu.org>, 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:59:00 -0000	[thread overview]
Message-ID: <20100829234708.GA39872@troutmask.apl.washington.edu> (raw)
In-Reply-To: <1283114926.2376.4.camel@localhost.localdomain>

On Sun, Aug 29, 2010 at 10:48:46PM +0200, Uros Bizjak wrote:
> 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...
> 

Thanks for the patch.  It is clearly a step in the right
direction.  Unfortunately, my build dies with fixtfti.c,
fixunstfti.c, floattitf.c, and floatuntitf.c, which I 
assume are used with conversions involving TI and TF modes.
If I use #if 0 ... #endif to block out the code in 
those files, my build proceeds to libgomp, which dies with
only two missing symbols,

/usr/home/kargl/gcc/obj4x/./gcc/libgcc_s.so: undefined reference to `__fabstf2'
/usr/home/kargl/gcc/obj4x/./gcc/libgcc_s.so: undefined reference to `__copysigntf3'

I suppose this means that on FreeBSD, I need to enable TI mode
as well as TF.

-- 
Steve

  reply	other threads:[~2010-08-29 23:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  1:55 Uros Bizjak
2010-08-30  1:59 ` Steve Kargl [this message]
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=20100829234708.GA39872@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ubizjak@gmail.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).