From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] openrisc: Add optimized memcpy routine
Date: Fri, 25 Mar 2016 12:18:10 +0000 [thread overview]
Message-ID: <56F52C82.8060905@embecosm.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1603250632270.5619@lianli.shorne-pla.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 24/03/16 22:06, Stafford Horne wrote:
<snip>
> This reply took me some time because I was spending the last few
> days looking into GCC. The openrisc GCC back end seems to need a
> rewrite before it can be upstreamed due to copyright issues. But we
> are still maintaining the port and keeping it up to date with
> upstream.
Hi Stafford,
I thought BlueCmd had resolved almost all of the copyright issues, by
talking to most of the copyright holders. So I didn't think there was
much that needed rewriting. Certainly there is no restriction to
anything done by Joern Rennecke (amylaar) as part of the major work he
did on GCC 4.5.1 a few years ago.
I don't think Joern is on this mailing list, but I'm sure he'll be
happy to review any OpenRISC GCC work.
Best wishes,
Jeremy
- --
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email: jeremy.bennett at embecosm.com
Web: www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlb1LIIACgkQvvWBcvtHVOG5qACgiAWUC/vU8Z9qkapBtujAIHVx
wpwAnjoidh1Pkz7lgnmfjVlyXkas6iXW
=7ZAg
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2016-03-25 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 14:29 [OpenRISC] [RFC PATCH] Optimized memcpy routine Stafford Horne
2016-03-21 14:29 ` [OpenRISC] [PATCH] openrisc: Add optimized " Stafford Horne
2016-03-23 4:54 ` Jonas Bonn
2016-03-24 22:06 ` Stafford Horne
2016-03-25 12:18 ` Jeremy Bennett [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:
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=56F52C82.8060905@embecosm.com \
--to=jeremy.bennett@embecosm.com \
--cc=openrisc@lists.librecores.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