From: whitequark <whitequark@whitequark.org>
To: Philipp Wagner <lists@philipp-wagner.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Chen Liqin <liqin.linux@gmail.com>,
"open list:QUALCOMM HEXAGON..." <linux-hexagon@vger.kernel.org>,
Richard Kuo <rkuo@codeaurora.org>,
David Howells <dhowells@redhat.com>,
openrisc@lists.librecores.org, Lennox Wu <lennox.wu@gmail.com>,
James Hogan <jhogan@kernel.org>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
"open list:METAG ARCHITECTURE" <linux-metag@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [OpenRISC] Removing architectures without upstream gcc support
Date: Mon, 26 Feb 2018 15:24:25 +0000 [thread overview]
Message-ID: <9dda26a68c1174933e456227efb6ae01@whitequark.org> (raw)
In-Reply-To: <57602e7e-a9c6-3480-7e99-7d274e836ed6@philipp-wagner.com>
On 2018-02-26 12:10, Philipp Wagner wrote:
> Actually the LLVM port of or1k isn't upstream either. CCing
> whitequark, who might know more about the (non-)plans of getting the
> backend upstream. I also don't know of anyone having tried to build
> the openrisc kernel with LLVM, would certainly be an interesting thing
> to try.
I keep the OR1K backend up-to-date and generally in good shape (e.g.
I've got exception handling work and added all missing instructions
to the internal assembler) but upstreaming it is many weeks of work
that I personally cannot spare, and the LLVM community requests that
those who upstream backends maintain buildbots running hardware tests
indefinitely, which I personally cannot afford.
--
whitequark
next prev parent reply other threads:[~2018-02-26 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK8P3a2-6YwRR3j7J78fVHSvDpq8Kf4wRj6d9mnGgAxgkYypxg@mail.gmail.com>
[not found] ` <20180222234833.GA3047@roeck-us.net>
[not found] ` <CAK8P3a3Y2b-DivYz1ZqhFGUqQaiF=5SDB6RFLtCknwY2--09OQ@mail.gmail.com>
[not found] ` <20180223154316.35b26857@alans-desktop>
[not found] ` <20180223171019.GA1125@roeck-us.net>
[not found] ` <20180225202806.735a6870@alans-desktop>
2018-02-25 22:50 ` Removing architectures without upstream gcc support Pavel Machek
[not found] ` <155284c9-7fd4-2f2c-0216-1c43622f88c3@philipp-wagner.com>
2018-02-26 8:00 ` [OpenRISC] " Arnd Bergmann
2018-02-26 12:10 ` Philipp Wagner
2018-02-26 15:24 ` whitequark [this message]
[not found] ` <2d12dc77-16b9-417d-72e3-2b1ffa38803d@gmail.com>
2018-02-26 8:26 ` Arnd Bergmann
2018-02-26 22:11 ` Eric W. Biederman
[not found] ` <20180222191758.GB5180@codeaurora.org>
[not found] ` <CAK8P3a3r=3wDtqV5feLUT-hOkE+9yWOLjLVm+nejqdaN7MtMFw@mail.gmail.com>
2018-02-28 2:06 ` Richard Kuo
2018-02-28 8:37 ` Arnd Bergmann
2018-03-03 1:43 ` Richard Kuo
[not found] ` <20180222160217.GA18243@infradead.org>
[not found] ` <CAMo8BfLoqat+6CyOM2VV5Wz13NFMj54YisCogiVm95oDwdnTFQ@mail.gmail.com>
[not found] ` <20180222180420.GA17956@infradead.org>
[not found] ` <CAK8P3a2VMbAARCFuBjY7TMuAfGM_h4BU3PfQA2C_pUFT34UHAA@mail.gmail.com>
2018-02-28 8:59 ` Florian Weimer
2018-03-09 14:00 ` Xuetao Guan
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=9dda26a68c1174933e456227efb6ae01@whitequark.org \
--to=whitequark@whitequark.org \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=jhogan@kernel.org \
--cc=jonas@southpole.se \
--cc=lennox.wu@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--cc=lists@philipp-wagner.com \
--cc=openrisc@lists.librecores.org \
--cc=rkuo@codeaurora.org \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).