From: Joseph Myers <joseph@codesourcery.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Xianmiao Qu <xianmiao_qu@c-sky.com>, Han Mao <han_mao@c-sky.com>,
Yunhai Shang <yunhai_shang@c-sky.com>
Subject: Re: [0/5] C-SKY port
Date: Thu, 26 Jul 2018 23:04:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1807262258320.6526@digraph.polyomino.org.uk> (raw)
In-Reply-To: <a8120cc2-833b-0f4f-6085-0500838a13cb@codesourcery.com>
On Tue, 24 Jul 2018, Sandra Loosemore wrote:
> On 07/23/2018 10:17 PM, Sandra Loosemore wrote:
>
> > C-SKY proposes Han Mao <han_mao@c-sky.com> and Yunhai Shang
> > <yunhai_shang@c-sky.com> as maintainers for this port.
>
> I apologize, I made a mistake here. The correct proposed maintainers are
> Xianmiao Qu <xianmiao_qu@c-sky.com> and Yunhai Shang
> <yunhai_shang@c-sky.com>.
I'd like to confirm: will the maintainers be running a bot reporting test
results for trunk for at least one C-SKY configuration to gcc-testresults
(daily or thereabouts), and monitoring results for regressions and
addressing those regressions promptly? We don't yet have such a
requirement, but when an architecture-independent patch causes failures on
a particular architectures, it's much better if the architecture
maintainers raise the issue while the patch is still fresh in the author's
mind (meaning within a few days at most of the commit) than if they only
look at results and track down the patch causing the failure many months
later (e.g. while reviewing test results in preparation for the following
release).
> > We expect that
> > C-SKY will also be providing a public link to the processor and ABI
> > documentation at some point.
>
> The ABI manual has been posted, but not the ISA documentation yet. (I'd guess
> that when it does show up it will be in the same place, though.)
>
> https://github.com/c-sky/csky-doc
Could you provide the proposed GCC website changes for the port
(backends.html, readings.html, news item for index.html)? readings.html,
in particular, would link to the ABI and ISA documentation, while
backends.html gives summary information about the properties of both the
architecture and the GCC port.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-07-26 23:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 4:17 Sandra Loosemore
2018-07-24 4:20 ` [1/5] C-SKY port: Configury Sandra Loosemore
2018-07-24 15:09 ` Jeff Law
2018-07-24 4:21 ` [2/5] C-SKY port: Backend implementation Sandra Loosemore
2018-07-24 15:45 ` Jeff Law
2018-07-24 18:19 ` Sandra Loosemore
2018-07-24 21:25 ` Jeff Law
2018-07-25 0:17 ` Sandra Loosemore
2018-07-25 4:50 ` Jeff Law
2018-07-25 13:17 ` Paul Koning
2018-07-25 14:54 ` Sandra Loosemore
2018-07-26 6:07 ` 瞿仙淼
2018-07-28 1:49 ` Sandra Loosemore
2018-08-02 22:33 ` Jeff Law
2018-08-02 22:28 ` Jeff Law
2018-08-03 7:58 ` Yunhai
2018-08-03 16:26 ` Sandra Loosemore
2018-07-24 4:23 ` [3/5] C-SKY port: Documentation Sandra Loosemore
2018-07-24 15:10 ` Jeff Law
2018-07-24 4:25 ` [4/5] C-SKY port: Testsuite Sandra Loosemore
2018-07-24 15:10 ` Jeff Law
2018-07-24 4:26 ` [5/5] C-SKY port: libgcc Sandra Loosemore
2018-07-24 15:12 ` Jeff Law
2018-07-24 18:10 ` Segher Boessenkool
2018-07-24 18:19 ` Sandra Loosemore
2018-07-24 19:46 ` Segher Boessenkool
2018-07-24 15:23 ` [0/5] C-SKY port Sandra Loosemore
2018-07-26 23:04 ` Joseph Myers [this message]
2018-07-30 16:59 ` Sandra Loosemore
2018-08-01 14:28 ` 瞿仙淼
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=alpine.DEB.2.20.1807262258320.6526@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=han_mao@c-sky.com \
--cc=sandra@codesourcery.com \
--cc=xianmiao_qu@c-sky.com \
--cc=yunhai_shang@c-sky.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).