From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001545] ustl: update to uSTL 1.6
Date: Sun, 25 Mar 2012 15:46:00 -0000 [thread overview]
Message-ID: <20120325154548.C93BB2F7800B@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001545-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001545
John Dallaway <john@dallaway.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |john@dallaway.org.uk
--- Comment #1 from John Dallaway <john@dallaway.org.uk> 2012-03-25 16:45:46 BST ---
Sergei, great to see this patch. Thank you.
The patch looks clean. You have replaced the NextPow2 implementation with the
latest from upstream which is good. Our efforts to minimise the differences
between eCos uSTL sources and upstream are working well for us.
If the tests are building and running OK with GCC 4.3.2 tools (default template
+ ustl + fileio), then I see no reason why you should not check this in. It is
always good to check uSTL with a target architecture other than x86 since Mike
Sharov works mainly with x86. We know that a few of the tests are interactive
and will therefore not run.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-03-25 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 16:12 [Bug 1001545] New: " bugzilla-daemon
2012-03-25 15:46 ` bugzilla-daemon [this message]
2012-03-25 16:18 ` [Bug 1001545] " bugzilla-daemon
2012-04-04 18:12 ` bugzilla-daemon
2012-04-04 18:28 ` bugzilla-daemon
2012-04-04 18:59 ` bugzilla-daemon
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=20120325154548.C93BB2F7800B@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.org \
/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).