From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards To: Jonathan Larmour Cc: ecos Subject: Re: [ECOS] sprintf test failure? Date: Wed, 17 Nov 1999 12:16:00 -0000 Message-id: <19991117141628.A8390@visi.com> References: <19991115142256.A20950@visi.com> <19991115150147.A21889@visi.com> <383090E1.EA239C9D@cygnus.co.uk> X-SW-Source: 1999-11/msg00055.html 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