From f30992d46d166a62fb5dbb5b86b625ee019a7107 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Tue, 30 Sep 2003 19:12:20 +0000 Subject: 2003-09-30 Andrew Cagney * mi-main.c: Rename REGISTER_VIRTUAL_SIZE to DEPRECATED_REGISTER_VIRTUAL_SIZE. 2003-09-30 Andrew Cagney * gdbarch.sh (DEPRECATED_REGISTER_VIRTUAL_SIZE): Rename REGISTER_VIRTUAL_SIZE. * gdbarch.h, gdbarch.c: Regenerate. * vax-tdep.h, sparc-tdep.c, regcache.h: Update. * regcache.c, mn10300-tdep.c, mips-tdep.c: Update. * infcmd.c, frame.c, findvar.c, cris-tdep.c: Update. 2003-09-30 Andrew Cagney * gdbint.texinfo (Target Architecture Definition): Rename REGISTER_VIRTUAL_SIZE to DEPRECATED_REGISTER_VIRTUAL_SIZE. (Target Architecture Definition): --- gdb/regcache.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'gdb/regcache.h') diff --git a/gdb/regcache.h b/gdb/regcache.h index 69ed4e62..9a341c3 100644 --- a/gdb/regcache.h +++ b/gdb/regcache.h @@ -147,8 +147,8 @@ extern struct type *register_type (struct gdbarch *gdbarch, int regnum); 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: + used? As a rule of thumb, use DEPRECATED_REGISTER_VIRTUAL_SIZE in + cooked code, but with the comment: OK: REGISTER_VIRTUAL_SIZE -- cgit v1.1