Re: Gnutools: consideration for upgrade to GCC 4.6

[Ilija Kocho <ilijak@siva.com.mk>]

Hi Alex

I wish to thank eCosCentric for supporting eCos GCC 4.6 release. It will 
both assure quality of this release and strengthen the image of eCos 
community toolchain.

In order to best utilize 2 lab. weeks of testing we should have well 
prepared binaries. In my view, it would be the best to carry out the 
eCosCentric lab. test as final release verification step after some 
field testing. In a course of field testing we shall also prepare eCos 
itself, (eliminate warnings, etc.).

Regarding targets, I don't have objections. However you may find 
interesting Freescale K70 (Cortex-M4F)
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-K70F120M&parentCode=K70&fpsp=1
mainly because of single precision FPU support. Btw hard-float library 
support for Cortex-M4F will be new feature in this GCC release.
I must admit that we don't have BSP yet as this is brand new chip but am 
working on it and expect to have it in short time.

Note: The considerations above are my personal. I would appreciate 
suggestions from other maintainers and developers.

We'll keep you up to date with the progress.

Regards

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
>
>