ColdFire/fido support

Vladimir Prus vladimir@codesourcery.com
Sun May 6 11:52:00 GMT 2007


On Saturday 05 May 2007 15:02, Andreas Schwab wrote:
> Vladimir Prus <vladimir@codesourcery.com> writes:
> 
> > +  /* Is this ColdFire architecture, as opposed to generic m68k?  */
> > +  int coldfire;
> > + 
> > +  /* Is this fido architecture, as opposed to generic m68k?  */
> > +  int fido;
> 
> How about making this a single enum?  They surely can never both be
> non-zero at the same time.

Good idea. Here's a revised patch.

Thanks,
Volodya

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.diff
Type: text/x-diff
Size: 13793 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20070506/a2f4895d/attachment.bin>
-------------- next part --------------
	* m68k-tdep.h (enum m68k_flavour): New.	
	(struct gdbarch_tdep): New fields
	float_return, fpreg_type, flavour and
	fpregs_present.
	* m68k-tdep.c (m68k_register_type): Use
	fpregs_present and fpreg_type.
	(m68k_register_names): New.
	(m68k_register_name): Use the above.
	(m68k_convert_register_p): Consult fpregs_present.
	(m68k_register_to_value, m68k_value_to_register):
	Use register_type to obtain the type of floating
	point registers.
	(m68k_svr4_extract_return_value): Check tdep->float_return.
	Use register_type to get the type of floating
	point regiters.
	(m68k_svr4_store_return_value): Likewise.
	(m68k_dwarf_reg_to_regnum): Check tdep->fpregs_present.
	(m68k_analyze_register_saves): Likewise.
	(m68k_gdbarch_init): Extract infromation
	from XML description, if present.  Guess coldfire by
	looking at the file, if present. Conditionalize
	setting of long double format.  Set decr_pc_after_break
	to 2 on coldfire and fido.  Enable XML-driven
	register description.
	* m68kbsd-tdep.c (m68kbsd_fpreg_offset): Use
	size of tdep->fpreg_type, as opposed to hardcoded value.


More information about the Gdb-patches mailing list