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]

[PATCH] monitor_ops regnames array


With multi-arch NUM_REGS is not a constant, but monitor.c was treating
as a constant in determining the size of the numregs array. So I added
a function to monitor_ops that returns the register names, and doesn't
need NUM_REGS to be constant.
I only changed the rom files that are compiled for the m68k, but the
array is still there.

ok to commit?

grace

2002-06-25  Grace Sainsbury  <graces@redhat.com>
	    
	    * monitor.h: Add the function regname to monitor_ops
	    structure. This way NUM_REGS does not have to be a
	    constant.
	    * monitor.c (monitor_fetch_register): Added support for
	    regname
	    function. The function is called if the array regnames is
	    NULL.
	    (monitor_store_register): Same.
	    * cpu32bug-rom.c (cpu32bug_regname):  Add
	    function. Replaces regnames array.
	    (init_cpu32bug_cmds): set cpu32bug_cmds.regnames to NULL,
	    cpu32bug_cmds.regname to point to new function.
	    * abug-rom.c (abug_regname): Same as above.
	    (init_abug_cmds): Same.
	    * dbug-rom.c (dbug_regname): Same as above.
	    (init_dbug_cmds): Same.
	    * remote-est.c (est_regname): Same. 
	    (init_est_cmds): Same.
	    * rom68k-rom.c (rom68k_regname): Same. 
	    (init_rom68k_cmds): Same.

Attachment: newpatch.patch
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]