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] |
I find the naming convention for the hppa targets too short for my liking: - hppah -> hppa on hpux - hppao -> hppa on osf - hppab -> hppa on bsd
What about the other way. panbsd-tdep.c pa-linux-tdep.c pa-hpux-nat.c for reasons unknown gdb ended up with config/pa instead of config/hppa.
but which ever. (To follow up eli's comment, watch the ari for name space problems).I suggest we transition to a more verbose naming, which should be more consistent with the other ports I know. For instance, how about hppa-hpux instead of hppah. I hear a netbsd port will probably be done in the future, we can then use hppa-netbsd. We would use this convention for the files in the config/pa directory (tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb (hppa-hpux-tdep.c). The part that is indenpedent of the OS would still stay in hppa (eg tm-hppa, hppa-tdep.c, etc). Does this seam like a good idea?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |