From: Stafford Horne <shorne@gmail.com>
To: Stafford Horne <shorne@gmail.com>,
cgen@sourceware.org, gdb-patches@sourceware.org,
openrisc@lists.librecores.org
Subject: Re: [PATCH] cgen: sim: Updates to sim files to match gdb types
Date: Mon, 02 May 2016 23:50:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.20.1605030849020.2230@lianli.shorne-pla.net> (raw)
In-Reply-To: <20160502182904.GJ26300@vapier.lan>
(Replying second time without the crazy text/html) sorry about that.
On Mon, 2 May 2016, Mike Frysinger wrote:
> On 01 May 2016 15:03, Mike Frysinger wrote:
>> On 01 May 2016 11:18, Stafford Horne wrote:
>>> The types like MACH and MODEL have changes to SIM_MACH and SIM_MODEL
>>> make updates to match these changes. This way people dont have to
>>> manually update the generated files in GDB.
>>>
>>> I am from openrisc and working on getting the openrisc sim and gdb patches
>>> ready for submitting to upstream. This was required to get the sim build to
>>> work.
>>
>> looks fine to me (since i did make those changes in the sim), but i'm not
>> a cgen committer.
>
> i talked to Frank and i'll pick this up.
Thank you
> cgen is still using the CVS tree right ?
Yes, as far as I know I can only find cgen in cvs. This patch is based on
the nightly release from 20160401 (I didn't have a cvs client on my
machine) so it should apply find against current CVS. Let me know if you
have any issues.
prev parent reply other threads:[~2016-05-02 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 2:19 Stafford Horne
2016-05-01 19:03 ` Mike Frysinger
2016-05-02 18:29 ` Mike Frysinger
2016-05-02 23:50 ` Stafford Horne [this message]
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.LFD.2.20.1605030849020.2230@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=cgen@sourceware.org \
--cc=gdb-patches@sourceware.org \
--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 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).