From: "Frank Ch. Eigler" <fche@redhat.com>
To: Evgeny Belyanco <esp1@kbkcc.ru>
Cc: sid@sources.redhat.com, ecos-discuss@ecos.sourceware.org
Subject: Re: SID for PowerPC
Date: Thu, 13 Jul 2006 20:12:00 -0000 [thread overview]
Message-ID: <20060713201205.GB20476@redhat.com> (raw)
In-Reply-To: <44584221.20060713234622@kbkcc.ru>
Hi -
> FCE> Sorry, no, we have not completed a port of a PowerPC core
> FCE> simulator to sid.
>
> Is it any plan for complete this (within '06-07 years)?
I am not aware of any.
> I have no skills in SID now, but how I can help this? [...]
Depending on your interest and expertise, various options include:
- finding a way of using gdb's psim instead
- continuing Johan Rydberg's powerpc cpu model sketch in cgen/cpu/powerpc.cpu
- FChE
next prev parent reply other threads:[~2006-07-13 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 21:09 [patch][rfa] Don't Generate Code to Support Unused Write Stacks Dave Brolley
2006-07-12 21:53 ` SID for PowerPC Evgeny Belyanco
2006-07-13 19:10 ` Frank Ch. Eigler
2006-07-13 19:47 ` Re[2]: " Evgeny Belyanco
2006-07-13 20:12 ` Frank Ch. Eigler [this message]
2006-07-12 23:20 ` [patch][rfa] Don't Generate Code to Support Unused Write Stacks Frank Ch. Eigler
2006-07-13 18:43 ` Dave Brolley
2006-07-14 18:54 ` Dave Brolley
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=20060713201205.GB20476@redhat.com \
--to=fche@redhat.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=esp1@kbkcc.ru \
--cc=sid@sources.redhat.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).