From: Max Filippov <jcmvbkbc@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] xtensa: new target architecture for qemu
Date: Sat, 30 Apr 2011 16:42:36 +0400 [thread overview]
Message-ID: <BANLkTi=EAbwtm5Nu0iicFL5_GeDj74ey9g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=Z+RZV2pRYeqLSYe_Cofp0QRWnCQ@mail.gmail.com>
>>> - if possible, simcall should become a linux-user target instead
>>
>> simcall is used in freestanding libc provided by Tensilica, I guess
>> primarily to ease OS-less development. I can make it an additional
>> option, but it seems impractical to remove it completely.
>
> Does that still emulate devices? In that case it would be like
> semihosting mode in ARM, so it would be OK to stay where you put it.
It only provides very limited support for file I/O, argc/argv passing
and profiling/gdb related magic which I'm not going to implement.
Thanks.
-- Max
prev parent reply other threads:[~2011-04-30 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 21:08 [Qemu-devel] xtensa: new target architecture for qemu Max Filippov
2011-04-30 7:07 ` Blue Swirl
2011-04-30 8:24 ` Max Filippov
2011-04-30 9:06 ` Blue Swirl
2011-04-30 10:25 ` Peter Maydell
2011-04-30 12:47 ` Max Filippov
2011-04-30 12:42 ` Max Filippov [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='BANLkTi=EAbwtm5Nu0iicFL5_GeDj74ey9g@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).