This is the mail archive of the 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]

Re: How do I replace DEPRECATED_TM_FILE?

On Thu, Jun 21, 2007 at 06:33:42PM +0100, Joern Rennecke wrote:
> except for ARC_RET_REGNUM and ARC_ORIG_R8_REGNUM, these registers
> exist also for the embedded target, but with different numbers;
> the embedded target allos access to numerous extra auxilary registers.

Which registers are available to talk to is a property of the target;
you might want to look at target descriptions, which have been my
project for the last year or two.  Which ones a DWARF number refers to
are a gdbarch property.

> > That determines the answer to your question.  If it's the dwarf2
> > mapping, for instance, you'd put overrides in an OS/ABI sniffer in the
> > Linux tdep file.
> > 
> > I've done a lot of work lately to isolate GDB's internal register
> > numbering from various external numberings.  You can probably use the
> > same internal registers in most places now.
> Another difference is the osabi setting.  arc_gdbarch_init also calls
> different functions for the different subtargtes to set a number of other
> settings.

No, I mean, you use the OSABI setting to determine which set of dwarf
registers you mean.  I don't know what you meant by "another
difference is the OSABI setting"; you should not be setting the OSABI
in your arc_gdbarch_init, you should be using the normal sniffers and
letting gdbarch_init_osabi dispatch appropriately.

Daniel Jacobowitz

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