From: Ilija Kocho <ilijak@siva.com.mk>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: John Dallaway <john@dallaway.org.uk>,
Jonathan Larmour <jifl@eCosCentric.com>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>,
Sergei Gavrikov <sergei.gavrikov@gmail.com>
Subject: Re: [ECOS] Fwd: [ECOS] eCos arm-eabi GNU tools - test release 4.6.3-20120623
Date: Mon, 30 Jul 2012 09:38:00 -0000 [thread overview]
Message-ID: <50165611.8000202@siva.com.mk> (raw)
In-Reply-To: <50127D75.8060507@ecoscentric.com>
Hi Alex
Thanks for report.
ustl has been upgraded recently
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001545
so we need to check if that is ustl or compiler or both.
Unfortunately I have no LPC2468, or any target other than Cortex-M handy.
I'm adding Sergei to the CC, I hope he may have some insight.
Thanks
Ilija
On 27.07.2012 13:37, Alex Schuilenburg wrote:
> Hi Ilija,
>
> On 2012-06-26 12:44, Ilija Kocho wrote:
>> Hi Alex
>>
>> As announced by John we have new test release of the GNU tools. This
>> release fixes the issues found in previous test releases in both GCC and
>> GDB so we can continue with testing.
>> Therefore I would ask you to put it on eCosCentric test farm. The
>> details for download and installation are below.
> The 4.6.3-20120623 arm tools are now in the farm running on the stm3210e
> eval board and lpc2468. Actually, I had the lpc2468 start in the farm a
> while ago but failed to monitor the results - they were all timing out
> because the old anoncvs redboot I built in March 2012 is now
> incompatible with the current anoncvs. Obviously RedBoot is now updated.
>
> One big issue is that the ustl permutation fails with every test on the
> lpc2468 for both arm and thumb. The tests fail to start - they either
> dont hit the cyg_test_init breakpoint or they fail with SIGBUS or, if
> they do hit cyg_test_start, they crash and burn afterwards with another
> SIGBUS. I have terminated all ustl tests for the lp2468 as a result as
> they simply slow things down. Unfortunately, excluding the ustl
> failures, the failure rate is currently 13 out of 484 tests run so far.
> I'll post a more complete list when it has run 5000 or more tests.
>
> The stm3210e is faring a lot better. 1113 tests run so far and only 6
> failures: ustl tests that have failed so far are bvt05, bvt13, bvt17 and
> sprintf2. Both testintr and kexcept1 are failing in other perms as before.
>
> -- Alex
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2012-07-30 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 11:08 John Dallaway
2012-06-26 11:44 ` [ECOS] Fwd: " Ilija Kocho
2012-07-27 11:37 ` Alex Schuilenburg
2012-07-30 9:38 ` Ilija Kocho [this message]
2012-07-30 10:09 ` Sergei Gavrikov
2012-07-31 11:48 ` Alex Schuilenburg
2012-06-26 21:50 ` [ECOS] " David Fernandez
2012-06-27 7:00 ` John Dallaway
2012-06-27 11:29 ` David Fernandez
2012-06-27 12:09 ` Ilija Kocho
2012-06-27 16:22 ` David Fernandez
2012-06-27 16:38 ` Stanislav Meduna
2012-06-27 16:49 ` Ilija Kocho
2012-06-28 20:05 ` David Fernandez
2012-06-28 20:01 ` David Fernandez
2014-06-13 10:25 ` [ECOS] eCos arm-eabi GNU tools - " John Dallaway
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=50165611.8000202@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=alexs@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jifl@eCosCentric.com \
--cc=john@dallaway.org.uk \
--cc=sergei.gavrikov@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).