This is the mail archive of the gdb-patches@sourceware.org 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: PATCH: Cache types from target description

From: Daniel Jacobowitz <dan at codesourcery dot com>
To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
Cc: hjl dot tools at gmail dot com, gdb-patches at sourceware dot org
Date: Wed, 10 Feb 2010 16:01:36 -0500
Subject: Re: PATCH: Cache types from target description
References: <20100205011447.GA28263@lucon.org> <20100208185454.GA21449@lucon.org> <20100209154513.GA27404@lucon.org> <20100210183800.GA25489@caradoc.them.org> <201002102052.o1AKqvj4022421@glazunov.sibelius.xs4all.nl>

On Wed, Feb 10, 2010 at 09:52:57PM +0100, Mark Kettenis wrote:
> > Date: Wed, 10 Feb 2010 13:38:03 -0500
> > From: Daniel Jacobowitz <dan@codesourcery.com>
> > 
> > Really they should be described in the XML file!
> 
> 'fraid I don't agree with you on that.  When it comes to things like
> multi-bit flags, you want a real programming language.

How else would you do it?  I don't want the answer to be "in C, in
GDB"; we've got devices with dozens of complicated flag registers that
are specific to that one device.

I'm sure I could do it in Python, but it takes away the
self-describing property.  I'm not nuts enough to encapsulate the
Python in XML and execute untrusted code.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- PATCH: PATCH: Add builtin floating point types
  - From: H.J. Lu
- PATCH: Cache types from target description
  - From: H.J. Lu
- Re: PATCH: Cache types from target description
  - From: H.J. Lu
- Re: PATCH: Cache types from target description
  - From: Daniel Jacobowitz
- Re: PATCH: Cache types from target description
  - From: Mark Kettenis

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