This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> > Can I post new m32r files with deprecated functions and > > take care of their deprecated code later? > > Once the assignment is in place, they can certainly be posted. > Unfortunatly, they won't be accepted for the mainline until they pass > the `new architecture' acceptance criteria. Using code of d10v and other architecture you suggested, I've modified m32r files and removed all deprecated codes. To my surprise, new m32r-gdb began to work in only one day. I didn't think it would finish so soon. I attached the following new m32r files: m32r-tdep.c m32r-stub.c m32r-rom.c config/m32r/m32r.mt I also attached a patch file for configure.tgt. 2003-06-17 Kei Sakamoto <sakamoto.kei@renesas.com> * configure.tgt : Add m32r*-*-elf*. * m32r-rom.c, m32r-tdep.c m32r-tdep.c, config/m32r/m32r.mt: New files. I couldn't find the 'new architecture' acceptance criteria in gdb's documentation. So I'm not sure that the above files are acceptable for the mainline. At least they are multi-arched and do not contain deprecated code. If there is any problem, please let me know. Thank you, Kei Sakamoto
Attachment:
m32r-tdep.c
Description: Binary data
Attachment:
m32r-stub.c
Description: Binary data
Attachment:
m32r-rom.c
Description: Binary data
Attachment:
m32r.mt
Description: Binary data
Attachment:
configure.tgt.patch
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |