This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH RFC] Protoize m32r-stub.c, m88k-nat.c, m88k-tdep.c
- To: Kevin Buettner <kevinb at cygnus dot com>
- Subject: Re: [PATCH RFC] Protoize m32r-stub.c, m88k-nat.c, m88k-tdep.c
- From: jtc at redback dot com (J.T. Conklin)
- Date: 15 Sep 2000 10:50:25 -0700
- Cc: gdb-patches at sourceware dot cygnus dot com
- References: <1000915073306.ZM4195@ocotillo.lan>
- Reply-To: jtc at redback dot com
>>>>> "Kevin" == Kevin Buettner <email@example.com> writes:
Kevin> I did three files this time because there was only one function that
Kevin> needed doing in each of them. (The m88k-*.c files bring back old
Kevin> memories; I first started hacking on gdb on an m88k box in the early
Kevin> * m32r-stub.c (prepare_to_step): Protoize.
Should we consider not protoizing the *-stub.c files? While these are
distributed with GDB, they are code that is going to be hacked to bits
as they are integrated into a remote target. While user is probably
using gcc, it may be reasonable to be as conservative we can when it
comes to these files...