From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [RFA/m32r] revised m32r-linux patch
Date: Thu, 30 Sep 2004 09:35:00 -0000 [thread overview]
Message-ID: <02bb01c4a6d0$d3245ac0$5169910a@E5A02646> (raw)
In-Reply-To: <200409281231.i8SCV1Od019519@juw15.nfra.nl>
Mark and Eli,
Thank you for your comments.
I fixed my patch. A list of changes are below.
- Replace TM_FILE with DEPRECATED_TM_FILE
- Use config/tm-linux.h instead of confif/m32r/tm-linux.h
- Remove config/m32r/tm-linux.h and config/m32r/m32r.mh
- Add m32r-linux-nat.c and m32r-linux-tdep.c to config/djgpp/fnchange.lst
- Stop using linux-proc.c
OK to commit now?
2004-09-30 Kei Sakamoto <sakamoto.kei@renesas.com>
Add m32r-linux support.
* configure.tgt: Add m32r*-*-linux*.
* Makefile.in (ALLDEPFILES): Add m32r-tdep.c, m32r-linux-nat.c
and m32r-linux-tdep.c.
(m32r-linux-nat.o, m32r-linux-tdep.o): New dependencies.
* m32r-tdep.c: Move some definitions to m32r-tdep.h.
* config/djgpp/fnchange.lst: Add m32r-linux-nat.c and
m32r-linux-tdep.c.
* m32r-tdep.h, m32r-linux-nat.c, m32r-linux-tdep.c,
config/m32r/linux.mh, config/m32r/linux.mt,
config/m32r/nm-linux.h: New files.
next prev parent reply other threads:[~2004-09-30 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 8:01 Fw: Unreviewed patch (m32r-linux support) Kei Sakamoto
2004-09-15 11:25 ` Mark Kettenis
2004-09-16 4:32 ` Kei Sakamoto
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 [this message]
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='02bb01c4a6d0$d3245ac0$5169910a@E5A02646' \
--to=sakamoto.kei@renesas.com \
--cc=gdb-patches@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