From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] multi-arching m32r
Date: Mon, 16 Jun 2003 10:33:00 -0000 [thread overview]
Message-ID: <028b01c333f2$d2a61db0$5169910a@KEI> (raw)
In-Reply-To: <3EBC1157.8070601@redhat.com>
Fri, 09 May 2003 16:36:39 -0400, Andrew Cagney wrote:
> > Hello,
> >
> > It seems that M32R is now obsoleted because it does not use
> > GDB's multi-arch framework. So I made it fully multi-arched.
> >
> > I attached a patch file created from insight-5.3 source files.
> > If there is something wrong with it, please let me know.
>
> Unfortunatly the 5.3 branch is dead. You'll need to:
>
> - get it building with current GDB
>
> - ensure that it contains no deprecated (or identified as deprecated)
> code (this means that it will need to use the new frame and inferior
> function call mechanism)
>
> Given that this will significantly change the file, and that the
> existing file is obsolete, I'd just post the new m32r files - don't
> bother with a diff.
>
> I also do not see any FSF assignment for either yourself or Renesas
> (Renesas is very new so I'm not suprized). If this needs to be aranged,
> then please contact me.
>
> Andrew
Andrew,
I sent back a Copyright Assignment form to FSF today. I also
built multi-arched m32r-gdb with current GDB snapshot. It works
fine.
But my m32r-tdep.c still contains many functions which are
identified as "deprecated". You mentioned new m32r files should
not contains no deprecated code. But it seems that most of
architecutures' files, except d10v and i386, contains deprecated
code.
Can I post new m32r files with deprecated functions and
take care of their deprecated code later? It is pretty
difficult to remove all deprecated code from m32r files
beacuse there are not much examples and documents about the
new frame and inferior function call mechanism now.
Kei Sakamoto
next prev parent reply other threads:[~2003-06-16 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 9:52 Kei Sakamoto
2003-05-09 20:36 ` Andrew Cagney
2003-06-16 10:33 ` Kei Sakamoto [this message]
2003-06-16 12:49 ` Andrew Cagney
2003-06-17 10:02 ` Kei Sakamoto
2003-06-17 14:32 ` Andrew Cagney
2003-07-02 1:09 ` Andrew Cagney
2003-07-04 0:10 ` Kei Sakamoto
2003-07-08 5:14 ` Kei Sakamoto
2003-07-08 6:10 ` Joel Brobecker
2003-07-08 6:18 ` Kei Sakamoto
2003-08-07 5:12 ` [commit] addition to gdb/MAINTAINERS Kei Sakamoto
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='028b01c333f2$d2a61db0$5169910a@KEI' \
--to=sakamoto.kei@renesas.com \
--cc=ac131313@redhat.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