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: Gnutools: consideration for upgrade to GCC 4.6
Date: Thu, 26 Jan 2012 13:36:00 -0000	[thread overview]
Message-ID: <4F2156B0.7080705@ecoscentric.com> (raw)
In-Reply-To: <4F206D2E.7040608@siva.com.mk>

Hi Ilija

On 2012-01-25 20:59, Ilija Kocho wrote:
> 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.

NP - it is a community effort after all :-)


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

We have the opposite view - our test farm finds errors which normal user
and field testing does not catch.  I think the earlier you get the
toolchain into the test farm the better because you will at least
minimise the user and field regression testing needed when you fix
issues thrown up by the farm.

We are happy to throw as many toolchain candidates as needed into the
test farm, with the only restriction being the bandwidth each board runs
the tests, so don't feel you have to hold back and use the farm for
final verification. Our test farm has thrown up far more eCos bugs and
toolchain issues than the rest of the community has to date.


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

That is interesting.  However the two boards I suggested are ones we
physically have so can build and run tests for and are conveniently
currently located in our test farm. We don't have a Freescale K70.  The
publicly available boards we do have can be found at
http://www.ecoscentric.com/ecos/ecospro_tab.shtml, although not all may
be available in our test farm. Is there board in this list you may think
may be better for testing for which a public eCos BSP exists?

Cheers

-- Alex Schuilenburg

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

  reply	other threads:[~2012-01-26 13:36 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 17:01 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-15 22:21         ` Ilija Kocho
2012-01-23  1:07           ` Jonathan Larmour
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 [this message]
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
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=4F2156B0.7080705@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).