This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: sprintf test failure?
On Mon, Nov 15, 1999 at 11:01:53PM +0000, Jonathan Larmour wrote:
>
> > > I don't think I'm going to actually be using sprintf with floating
> > > point numbers. All of the other libc tests seem to pass. Should I
> > > be concerned about the failures?
> >
> > 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.
> >
> > PASS:<acos() is stable>
> > PASS:<asin() is stable>
> > FAIL:<atan() failed tests> Line: 82, File: [...]/tests/vectors/atan.c
>
> The fact that some of them pass but not all of them makes me think a
> compiler bug (or more specifically, a miscompilation of libgcc, since that's
> where the soft float code lives).
>
> 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.
I'll make a note of that and perhaps build 2.95.2 tomorrow. I'm going
to need a faster computer if I'm going to start hacking on gcc.
> It could be a code generation issue with 2.95.1 or older binutils (less
> likely) - I don't know. Or it could be something to do with the
> big-endianness.
I should probably forget about the floating point stuff for now and
get back to work on the interrupt-driven serial port driver so that
I've got some relevent progress to report in the weekly staff meeting
tomorrow. :)
--
Grant Edwards
grante@visi.com