public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	GCC patches <gcc-patches@gcc.gnu.org>,
	Openrisc <openrisc@lists.librecores.org>,
	Jeff Law <law@redhat.com>,	Joseph Myers <joseph@codesourcery.com>,
	Joel Sherrill <joel@rtems.org>,
	Sebastian Huber <sebastian.huber@embedded-brains.de>,
	cgen@sourceware.org
Subject: Re: [PATCH v3 3/3] or1k: gcc: initial support for openrisc
Date: Tue, 30 Oct 2018 11:26:00 -0000	[thread overview]
Message-ID: <20181030112600.GA2843@lianli.shorne-pla.net> (raw)
In-Reply-To: <4ddf1c0d-76fb-8262-a6a2-afc7f8daee14@twiddle.net>

On Mon, Oct 29, 2018 at 04:42:43PM +0000, Richard Henderson wrote:
> On 10/29/18 4:34 PM, Segher Boessenkool wrote:
> > Is there some better documentation available?  This is what google found
> > for me.  I would have like better docs (more compact, etc.)  Links to
> > such would be great to have in readings.html :-)
> 
> https://openrisc.io/architecture
> 
> and especially the v1.2 pdf linked from there
> 
> https://raw.githubusercontent.com/openrisc/doc/master/openrisc-arch-1.2-rev0.pdf

Thanks,

I meant to point this out during my previous reply.  Also, I will send a patch
for adding this to wwwdocs.

  https://www.gnu.org/software/gcc/readings.html

-Stafford

  reply	other threads:[~2018-10-30 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181027043702.18414-1-shorne@gmail.com>
     [not found] ` <20181027043702.18414-4-shorne@gmail.com>
     [not found]   ` <20181028025730.GH5766@gate.crashing.org>
     [not found]     ` <ed59f12b-a2a3-fa28-0d03-de1d11bb6e42@twiddle.net>
2018-10-29 13:34       ` Stafford Horne
2018-10-29 16:35         ` Segher Boessenkool
2018-10-29 16:42           ` Richard Henderson
2018-10-30 11:26             ` Stafford Horne [this message]
2018-10-30 15:42               ` Segher Boessenkool

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=20181030112600.GA2843@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=cgen@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joel@rtems.org \
    --cc=joseph@codesourcery.com \
    --cc=law@redhat.com \
    --cc=openrisc@lists.librecores.org \
    --cc=rth@twiddle.net \
    --cc=sebastian.huber@embedded-brains.de \
    --cc=segher@kernel.crashing.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).