From: Doug Evans <dje@google.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v6 4/6] sim: or1k: add cgen generated files
Date: Wed, 18 Oct 2017 20:18:43 +0000 [thread overview]
Message-ID: <f403043532243a3ecc055bd7f204@google.com> (raw)
Stafford Horne writes:
> These are the simulator files generated by cgen. These are split out
> from the main sim patch to make the patch easier to review and smaller.
>
> sim/ChangeLog:
>
> yyyy-mm-dd Stafford Horne <shorne@gmail.com>
> Peter Gavin <pgavin@gmail.com>
>
> * or1k/arch.c: Generated.
> * or1k/arch.h: Generated.
> * or1k/cpu.c: Generated.
> * or1k/cpu.h: Generated.
> * or1k/cpuall.h: Generated.
> * or1k/decode.c: Generated.
> * or1k/decode.h: Generated.
> * or1k/model.c: Generated.
> * or1k/sem-switch.c: Generated.
> * or1k/sem.c: Generated.
LGTM (just generated files).
Can you confirm these were generated from the current cpu/ork1* files?
I didn't notice any patches for them.
next reply other threads:[~2017-10-18 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:18 Doug Evans [this message]
2017-10-18 20:38 ` [OpenRISC] [PATCH v6 4/6] sim: or1k: add cgen generated files Stafford Horne
-- 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:36 ` [OpenRISC] [PATCH v6 4/6] sim: or1k: add cgen generated files 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=f403043532243a3ecc055bd7f204@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.