public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: law@cygnus.com
Cc: pbarada@wavemark.com, egcs@cygnus.com
Subject: Re: Soft float for i486
Date: Wed, 01 Jul 1998 10:51:00 -0000	[thread overview]
Message-ID: <13722.19910.625086.367098@glinda.cygnus.com> (raw)
In-Reply-To: <9090.899023151@hurl.cygnus.com>

Jeffrey A Law writes:
|   In message <199803140044.TAA22071@miacomet.wavemark.com>you write:
|   > 
|   > I'm trying to build a cross-compiler using egcs-980302, and I want to
|   > target a i486 chip that does NOT have floating point, and I don't want
|   > to emulate the instructions.
|   > 
|   > I've found the following fragment in gcc/config/a29k/t-a29kbare :
|   > 
|   > # These are really part of libgcc1, but this will cause them to be
|   > # built correctly, so... 
|   > 
|   > LIB2FUNCS_EXTRA = fp-bit.c dp-bit.c
|   > 
|   > dp-bit.c: $(srcdir)/config/fp-bit.c
|   > 	cat $(srcdir)/config/fp-bit.c > dp-bit.c
|   > 
|   > fp-bit.c: $(srcdir)/config/fp-bit.c
|   > 	echo '#define FLOAT' > fp-bit.c
|   > 	cat $(srcdir)/config/fp-bit.c >> fp-bit.c
|   > 
|   > 
|   > I'm just trying to figure a good place to put them (or should I just
|   > shove them in t-i386bare and be done with it)?
| Going over some of my old mail.  I never saw anyone respond to this.
| 
| 
| Yup.  That's the right place for them.

Actually, as it exists in egcs, config/fp-bit.c is not up to handling
the x86.  This is because config/fp-bit.c only handle 32 and 64 bit
floating point, and not the 80 bit fp that the x86 supports.  I know
that we've talked about doing this within Cygnus, but the changes are
not on the main branchline.

|   > Perhaps every target should have thos so -msoft-float will actually
|   > work for any target...
| It's a thought, at least for embedded targets, probably not worth it
| for native targets.
| 
| I'd be kind of suprised if more than a few embedded targets don't
| already handle the soft-float stuff.

You do get better fp performance if you are not trapping to the kernel 
(assuming you have a kernel) to do the emulation, but instead just
calling the routine directly.

| jeff

      reply	other threads:[~1998-07-01 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-13 18:29 Peter Barada
1998-03-16 20:25 ` Jim Wilson
1998-06-28  2:05 ` Jeffrey A Law
1998-07-01 10:51   ` Michael Meissner [this message]

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=13722.19910.625086.367098@glinda.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=pbarada@wavemark.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).