From: Stafford Horne via Libc-alpha <libc-alpha@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Openrisc <openrisc@lists.librecores.org>,
Stafford Horne via Libc-alpha <libc-alpha@sourceware.org>,
Christian Svensson <blue@cmd.nu>
Subject: Re: [PATCH 1/1] Initial support for OpenRISC
Date: Sat, 23 May 2020 07:32:18 +0900 [thread overview]
Message-ID: <20200522223218.GD75760@lianli.shorne-pla.net> (raw)
In-Reply-To: <alpine.DEB.2.21.2005222201450.10437@digraph.polyomino.org.uk>
On Fri, May 22, 2020 at 10:02:54PM +0000, Joseph Myers wrote:
> On Sat, 23 May 2020, Stafford Horne via Libc-alpha wrote:
>
> > For binutils and gcc require patches which are mentioned in the cover letter.
> > I will document.
>
> In my view the changes need to be upstream before the patch can go into
> glibc. We want to avoid the mess we had with MicroBlaze where the port
> turned out to depend on GCC patches that hadn't yet been upstreamed.
Notes, I don't think that will be a problem. Binutils patches are already
upstream. The GCC patches should be too before I send the V2 series (I just
need to push them).
-Stafford
next prev parent reply other threads:[~2020-05-22 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 11:36 [PATCH 0/1] OpenRISC port Stafford Horne via Libc-alpha
2020-05-22 11:36 ` [PATCH 1/1] Initial support for OpenRISC Stafford Horne via Libc-alpha
2020-05-22 12:56 ` Florian Weimer via Libc-alpha
2020-05-22 21:59 ` Stafford Horne via Libc-alpha
2020-05-22 22:02 ` Joseph Myers
2020-05-22 22:32 ` Stafford Horne via Libc-alpha [this message]
2020-06-10 20:17 ` Stafford Horne via Libc-alpha
2020-05-22 20:56 ` Joseph Myers
2020-05-22 21:31 ` Stafford Horne via Libc-alpha
2020-05-22 18:52 ` [PATCH 0/1] OpenRISC port Joseph Myers
2020-05-22 21:01 ` Stafford Horne via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200522223218.GD75760@lianli.shorne-pla.net \
--to=libc-alpha@sourceware.org \
--cc=blue@cmd.nu \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.com \
/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).