espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-08-05 21:50:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

2003-02-28 Andrew Cagney <cagney@redhat.com>

Browse Source 
* regcache.c (register_size): New function.
	* regcache.h (register_size): Declare
	* d10v-tdep.c: Use register_size instead of REGISTER_RAW_SIZE, use
	max_register_size instead of MAX_REGISTER_RAW_SIZE.
This commit is contained in:
Andrew Cagney
2003-02-28 17:47:43 +00:00
parent 4224873a5a
commit 08a617dae2
4 changed files with 53 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
gdb/regcache.h
View File

@ -129,6 +129,32 @@ extern struct type *register_type (struct gdbarch *gdbarch, int regnum);
extern int max_register_size (struct gdbarch *gdbarch);
/* Return the size of register REGNUM. All registers should have only
one size.
FIXME: cagney/2003-02-28:
Unfortunatly, thanks to some legacy architectures, this doesn't
hold. A register's cooked (nee virtual) and raw size can differ
(see MIPS). Such architectures should be using different register
numbers for the different sized views of identical registers.
Anyway, the up-shot is that, until that mess is fixed, core code
can end up being very confused - should the RAW or VIRTUAL size be
used? As a rule of thumb, use REGISTER_VIRTUAL_SIZE in cooked
code, but with the comment:
OK: REGISTER_VIRTUAL_SIZE
or just
OK
appended to the end of the line. */
extern int register_size (struct gdbarch *gdbarch, int regnum);
/* Save/restore a register cache. The registers saved/restored is
determined by the save_reggroup and restore_reggroup (although you
can't restore a register that wasn't saved as well :-). You can