public inbox for
 help / color / mirror / Atom feed
From: Bart Veer <>
To: John Dallaway <>
Subject: Re: eCos 3.0 beta 1 remaining issues
Date: Wed, 25 Mar 2009 14:37:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (message from John Dallaway on 	Wed, 25 Mar 2009 13:05:38 +0000)

>>>>> "John" == John Dallaway <> writes:

    >> John, Jifl: any objections to me checking in this fix?

    John> Looking at the CVS logs, Andrew's change of 2008-12-24 was
    John> part of series of check-ins targeting compiler warnings in
    John> general. None of the other changes involved modifying
    John> inlined functions so I expect this is an isolated
    John> regression.

    John> From my perspective, it is clearly desirable to fix this for
    John> 3.0 but it is indeed late in the release cycle so I would
    John> ask that you do perform a basic run-time sanity test against
    John> the ecos-v3_0-branch before committing it. Best to use one
    John> of the new pre-built eCos toolchains (GCC 4.3.2) for this.

Tested on m5272c3 and synthetic target, and checked in to the V3
branch and the trunk.


Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
  ** Visit us at ESC Silicon Valley <>  **
  ** Mar 31-2 Apr 2009, Booth 221, San Jose McEnery Convention Center **

      reply	other threads:[~2009-03-25 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 11:31 John Dallaway
2009-03-25 11:01 ` John Dallaway
2009-03-25 12:22   ` Bart Veer
2009-03-25 13:05     ` John Dallaway
2009-03-25 14:37       ` Bart Veer [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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