public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6]
Date: Fri, 02 Mar 2012 16:36:00 -0000	[thread overview]
Message-ID: <4F50F700.5080902@ecoscentric.com> (raw)
In-Reply-To: <4F39887A.5050905@siva.com.mk>

Hi Ilija,

On 2012-02-13 22:02, Ilija Kocho wrote:
> Hi Alex
>
> eCos GNU tools 4.6.2-20120125 (arm_eabi) binaries are ready for testing.
> John has placed them on FTP and by now most of the mirrors should have
> updated.
>
> I guess this one is closest to you:
> http://www.mirrorservice.org/sites/sourceware.org/pub/ecos/gnutools/i386linux/test/ecos-gnutools-arm-eabi-20120125.i386linux.tar.bz2
>
> And here are the patches:
> http://www.mirrorservice.org/sites/sourceware.org/pub/ecos/gnutools/src/test/ecos-gnutools-20120125-patches.tar.bz2

Thanks.  I have taken a test snapshot of anoncvs on 2012-03-01
00:00:00:00 along with the toolchain above and thrown that to our test
farm.  Unfortunately the Embedded Artists LPC2468-32 anoncvs port
appears to be either incompatible with our RedBoot or is broken in
anoncvs.  All the tests fail to hit a breakpoint set at cyg_test_init,
or run without any breakpoints. I suspect this port appears to have
suffered bitrot since the V3 as the board appears to have been run in
our testfarm for the public eCos 3.0 release in 2009, and the RedBoot on
the board is dated Apr 25 2008  which goes back to V2.

I have just switched to using our eCosPro sources and the first couple
of tests I checked passed, so at least this confirms this is not any
issue with the toolchain. Using the same set of eCosPro sources with our
ecospro tools and the anoncvs tools at least will tell us if there is
any regression.  Unfortunately though, if there is a regression we will
only be able to report the test/s that failed along with the flags and
configuration used to build the tests.  Otherwise somebody is going to
need to fix the anoncvs port for the Embedded Artists LPC2468-32 board.


> The specific feature of public eCos is that it uses uSTL rather than
> stdlibc++. Would it be possible for you to add ustl with fileio tests?
> Should I be of any help please contact me.

I have added the configuration you sent to our test farm, although
obviously because the sources are eCosPro, there is no uSTL support
testing for the Embedded Artists LPC2468-32.

I'll let you know how we get on with the ST STM3210E-EVAL board testing.

Cheers
-- Alex
Managing Director/CEO                                eCosCentric Limited
www.ecoscentric.com             Reg in England and Wales, Reg No 4422071



>
> Cheers
> Ilija
>
>
>
> On 25.01.2012 13:29, Alex Schuilenburg wrote:
>> Hi Ilija
>>
>> eCosCentric are happy to make its eCos test farm available to you for
>> automated testing of the new toolchains.
>>
>> Having gone through our list of ARM and Cortex hardware in our test farm
>> and the hardware supported in the public eCos repository (i.e. the
>> physical hardware we have and what is supported in the public eCos
>> repository), we propose running tests for the Embedded Artists
>> LPC2468-32 (to test ARM7 and thumb mode, as well as the network stacks
>> with the newer toolchain since this board has ethernet support) and the
>> ST STM3210E-EVAL evaluation board (to test Cortex-M3).
>>
>> The tests will take around 2 weeks to run after which I will post the
>> results for you to examine.  The results will be accessible through a
>> web interface in three forms:
>>
>>  1. eCos build results
>>     eCos and its tests will be built in a number of different eCos
>>     configurations utilising a number of different compiler options.
>>     Each configuration is known as a perm (short for permutation).  A
>>     build is a tuple consisting of target+source+toolchain+perm.  The
>>     results of each build consist of the shell script used to configure
>>     and build eCos and the tests (so you can rebuild yourself), the eCos
>>     ecm export (so you can import the configuration without having to
>>     run the shell script), as well as the full compilation and link
>>     output of the build.
>>  2. eCos test results
>>     Each test built against a tuple is executed on real hardware with
>>     the test result logged. If a test fails, the full output is
>>     preserved and made available along with the test binary, although
>>     the full output of special tests such as tm_basic are also always
>>     made available.
>>  3. eCos test result summary
>>     The number of passes and number of each type of failure for each
>>     build is presented in table form to provide an overview of the test
>>     results for the build.
>>
>> All we need from you is a Linux hosted arm-eabi toolchain in tarball
>> form and the eCos sources, also in tarball form, although we can use
>> http://hg-pub.ecoscentric.com/ecos as the source base if you prefer.
>>
>> If you would like to make use of the test farm and agree with the
>> selection of targets (or can propose alternatives), please let me know
>> and provide me with the url where the toolchain can be downloaded from
>> (and optionally the sources).  I'll post the results as soon as the
>> tests are completed.
>>
>> Cheers
>>
>> --  Alex Schuilenburg
>>
>> Managing Director/CEO                                eCosCentric Limited
>> www.ecoscentric.com             Reg in England and Wales, Reg No 4422071
>>
>>
>>


  parent reply	other threads:[~2012-03-02 16:36 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 17:01 Gnutools: consideration for upgrade to GCC 4.6 Ilija Kocho
2012-01-13 18:54 ` Bernard Fouché
2012-01-13 19:39   ` Ilija Kocho
2012-01-13 19:09 ` Frank Pagliughi
2012-01-13 19:45   ` Ilija Kocho
2012-01-14 10:22 ` John Dallaway
2012-01-14 16:02   ` Sergei Gavrikov
2012-01-15 17:36     ` Grant Edwards
2012-01-15 18:42       ` Sergei Gavrikov
2012-01-15 21:39         ` Stanislav Meduna
2012-01-23  1:01           ` Jonathan Larmour
2012-01-15 22:21         ` Ilija Kocho
2012-01-23  1:07           ` Jonathan Larmour
2012-01-15 22:21         ` Ilija Kocho
2012-01-16 15:20         ` Grant Edwards
2012-01-16 20:43           ` Sergei Gavrikov
2012-01-16 21:11             ` Sergei Gavrikov
2012-01-17  9:58               ` Bernard Fouché
2012-01-17 10:38                 ` Paul Beskeen
2012-01-17 12:28                   ` Sergei Gavrikov
2012-01-23  0:59     ` Jonathan Larmour
2012-01-14 16:25   ` Ilija Kocho
2012-01-23  1:13     ` Jonathan Larmour
2012-01-23 18:40       ` Ilija Kocho
2012-01-23 19:29         ` Jonathan Larmour
2012-01-25 12:30         ` Alex Schuilenburg
2012-01-25 20:59           ` Ilija Kocho
2012-01-26 13:36             ` Alex Schuilenburg
2012-01-26 20:18               ` Ilija Kocho
2012-02-13 22:02           ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Ilija Kocho
2012-02-20 16:00             ` Alex Schuilenburg
2012-02-20 20:45               ` Ilija Kocho
2012-03-02 16:36             ` Alex Schuilenburg [this message]
2012-03-03 13:32               ` Ilija Kocho
2012-03-04  0:10                 ` Alex Schuilenburg
2012-03-04 17:49                   ` Sergei Gavrikov
2012-03-04 23:08                     ` Alex Schuilenburg
2012-03-04 19:37                   ` eCos GNU tools 4.6.2-20120125 ready for testing John Dallaway
2012-03-04 23:47                     ` Alex Schuilenburg
2012-03-05  8:00                       ` Sergei Gavrikov
2012-03-07 13:51                         ` Sergei Gavrikov
2012-03-07 11:58                       ` Alex Schuilenburg
2012-03-07 13:01                         ` Ilija Kocho
2012-03-07 13:39                           ` Sergei Gavrikov
2012-03-07 13:13                         ` John Dallaway
2012-03-12 16:43                           ` Alex Schuilenburg
2012-03-16 15:05                             ` Alex Schuilenburg
2012-03-08 17:28                         ` Alex Schuilenburg
2012-03-09  9:39                           ` Ilija Kocho
2012-03-09 17:15                             ` Alex Schuilenburg
2012-03-10 17:16                           ` John Dallaway
2012-03-12 16:12                             ` Alex Schuilenburg
2012-03-13 13:31                               ` Alex Schuilenburg
2012-03-13 14:16                                 ` Ilija Kocho
2012-03-13 17:47                                   ` Sergei Gavrikov
2012-03-15  8:50                                     ` John Dallaway
2012-03-17 14:50                                       ` Sergei Gavrikov
2012-03-17 20:58                                         ` John Dallaway
2012-03-17 16:44                                       ` Stanislav Meduna
2012-03-18 19:10                                   ` eCos GNU tools 4.6.3-20120315 [Was Re: eCos GNU tools 4.6.2-20120125 ready for testing] Ilija Kocho
2012-04-04 12:57                                     ` Lambrecht Jürgen
2012-04-04 13:18                                       ` Ilija Kocho
2012-05-31  8:42                                         ` eCos GNU tools 4.6.3-20120315 and link time optimization Bernard Fouché
2012-03-05  8:30                     ` eCos GNU tools 4.6.2-20120125 ready for testing Tomas Frydrych
2012-03-05  8:56                       ` Tomas Frydrych
2012-03-05  9:50                         ` John Dallaway
2012-03-05  9:55                           ` Anders Montonen
2012-03-05 14:20                             ` John Dallaway
2012-03-05 10:16                           ` Ilija Kocho
2012-03-05 12:56                             ` Tomas Frydrych
2012-03-03 12:58             ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Sergei Gavrikov
2012-01-17  9:37 ` Gnutools: consideration for upgrade to GCC 4.6 Tomas Frydrych
2012-01-17 16:10   ` Stanislav Meduna
2012-01-17 16:25     ` Tomas Frydrych
2012-01-17 16:45     ` Ilija Kocho
2012-01-20 14:42       ` Frank Pagliughi

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=4F50F700.5080902@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    /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).