public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@cygnus.co.uk>
Cc: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] sprintf test failure?
Date: Wed, 17 Nov 1999 12:16:00 -0000	[thread overview]
Message-ID: <19991117141628.A8390@visi.com> (raw)
In-Reply-To: <383090E1.EA239C9D@cygnus.co.uk>

On Mon, Nov 15, 1999 at 11:01:53PM +0000, Jonathan Larmour wrote:

> > I've also got some failures in libm (all of the failures were due to
> > results out of tolerance).  In my initial application, I doubt that I
> > will need any of the functions that failed, but if these failures are
> > due to something I did in my porting efforts, I'd like to get it
> > fixed.

> FWIW, I've compiled eCos with gcc 2.95.2 with a binutils snapshot of about
> two weeks ago. I built for ARM PID (arm7tdmi specifically), but
> little-endian. It works fine. I just went back and verified, and both
> sprintf1 and atan tests work.

Using gcc 2.95.2 and binutils-991018 (four weeks ago) still fails the
same tests on the Samsung board (ARM7tdmi big-endian).

> It could be a code generation issue with 2.95.1 or older binutils (less
> likely) - I don't know. 

It could theoretically be binutils (but I doubt it).

> Or it could be something to do with the big-endianness.

That's where I'd put my money if I were a betting man.

Any suggestions on tracking down the source of the problem, should I
choose to bet a few hours on that horse?

-- 
Grant Edwards
grante@visi.com


  parent reply	other threads:[~1999-11-17 12:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-15 12:23 Grant Edwards
1999-11-15 13:01 ` Grant Edwards
1999-11-15 13:31   ` Gary Thomas
1999-11-15 14:06     ` Grant Edwards
1999-11-15 14:08       ` Grant Edwards
1999-11-15 15:02   ` Jonathan Larmour
1999-11-15 15:37     ` Grant Edwards
1999-11-17 12:16     ` Grant Edwards [this message]
1999-11-17 12:46       ` Jonathan Larmour
1999-11-18  8:55         ` Grant Edwards
1999-11-18  9:01           ` Jonathan Larmour
1999-11-18 14:58             ` Jesper Skov
1999-11-18 15:07               ` Gary Thomas
1999-11-18 19:54         ` Grant Edwards
1999-11-17 14:09       ` Jesper Skov
1999-11-19 14:04         ` Grant Edwards
1999-11-19 15:40         ` Grant Edwards
1999-11-19 15:46           ` Jonathan Larmour
1999-11-19 16:40             ` Grant Edwards
1999-11-19 15:47           ` Jesper Skov
1999-11-19 15:50             ` Jonathan Larmour

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=19991117141628.A8390@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@cygnus.co.uk \
    /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).