From: Doug Evans <dje@google.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v6 0/6] sim port for OpenRISC
Date: Mon, 16 Oct 2017 18:04:22 +0000 [thread overview]
Message-ID: <001a113d092c0b7584055badd675@google.com> (raw)
Stafford Horne writes:
> On Fri, Oct 13, 2017 at 09:36:40PM +0900, Stafford Horne wrote:
>
> > Peter Gavin (3):
> > sim: cgen: add remainder functions (needed for OR1K lf.rem.[sd])
> > sim: cgen: add MUL2OFSI and MUL1OFSI functions (needed for OR1K
> > l.mul[u])
> > sim: testsuite: add testsuite for or1k sim
> >
> > Stafford Horne (3):
> > sim: or1k: add or1k target to sim
> > sim: or1k: add cgen generated files
> > sim: or1k: add autoconf generated files
> >
>
> Hello,
>
> As before the cgen and autoconf generated file patches did not get through, see
> details.
>
> ezmlm-reject: fatal: Sorry, I don't accept messages larger than 400000 bytes (#5.2.3)
>
> On my system:
>
> -rw-rw-r--. 1 shorne shorne 787935 Oct 13 08:12 v6-0004-sim-or1k-add-cgen-generated-files.patch
> -rw-rw-r--. 1 shorne shorne 495163 Oct 13 08:12 v6-0005-sim-or1k-add-autoconf-generated-files.patch
>
> If you are interested please pull from:
>
> https://github.com/stffrdhrn/binutils-gdb.git or1k-upstream-gdb-v8-sim-v6
>
> Else I can sent you private zipped copies.
As a data point I can (apparently) read them fine.
next reply other threads:[~2017-10-16 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 18:04 Doug Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-13 12:36 [OpenRISC] [PATCH v6 0/6] sim port for OpenRISC Stafford Horne
2017-10-13 12:46 ` Stafford Horne
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=001a113d092c0b7584055badd675@google.com \
--to=dje@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.