From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Mark Kettenis" <kettenis@jive.nl>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: Fw: Unreviewed patch (m32r-linux support)
Date: Thu, 16 Sep 2004 04:32:00 -0000 [thread overview]
Message-ID: <014a01c49ba6$31c6b900$5169910a@E5A02646> (raw)
In-Reply-To: <200409151125.i8FBPPCe013165@juw15.nfra.nl>
Mark,
Thank you for reviewing my patch.
> Anyway, before I start giving you more ill-guided advise,
Your advise is very well-guided. :-)
> Are there any plans to support the PTRACE_GETREGS/PTRACE_SETREGS
> requests? I really think a modern Linux port should support those
> (and only those), but Linux/M32R isn't going to support them, the code
> can be simplified even more.
It sounds reasonable. I'll implement PTRACE_GETREGS/PTRACE_SETREGS
on Linux/M32R kernel and simplify the register handling codes.
> Are there any plans to support a FPU?
Some chips of M32R have FPU. But their target is ECU (Engine Control
Unit) and does not support Linux because ECU doesn't need a large OS
like Linux. So FPU support is not necessary for Linux/M32R.
> Meanwhile I have a few more comments concerning m32r-linux-tdep.c.
OK. I'll revise my patch.
===
Kei Sakamoto
Renesas Technology Corp.
sakamoto.kei@renesas.com
next prev parent reply other threads:[~2004-09-16 4:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 8:01 Kei Sakamoto
2004-09-15 11:25 ` Mark Kettenis
2004-09-16 4:32 ` Kei Sakamoto [this message]
2004-09-16 13:59 ` Andrew Cagney
2004-09-28 10:04 ` [RFA/m32r] revised m32r-linux patch Kei Sakamoto
2004-09-28 12:31 ` Mark Kettenis
2004-09-30 9:35 ` Kei Sakamoto
2004-10-01 0:20 ` Kei Sakamoto
2004-10-01 7:18 ` Mark Kettenis
2004-10-01 7:33 ` [commit/m32r] " Kei Sakamoto
2004-09-28 19:53 ` [RFA/m32r] " Eli Zaretskii
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='014a01c49ba6$31c6b900$5169910a@E5A02646' \
--to=sakamoto.kei@renesas.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@jive.nl \
/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