From: Daniel Jacobowitz <dan@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: hjl.tools@gmail.com, gdb-patches@sourceware.org
Subject: Re: PATCH: Cache types from target description
Date: Wed, 10 Feb 2010 21:01:00 -0000 [thread overview]
Message-ID: <20100210210135.GY9493@caradoc.them.org> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2010-02-10 21:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 1:15 PATCH: PATCH: Add builtin floating point types H.J. Lu
2010-02-07 21:52 ` Mark Kettenis
2010-02-07 22:00 ` H.J. Lu
2010-02-07 22:14 ` Daniel Jacobowitz
2010-02-07 22:25 ` H.J. Lu
2010-02-07 23:03 ` H.J. Lu
2010-02-07 23:08 ` Daniel Jacobowitz
2010-02-08 2:17 ` H.J. Lu
2010-02-08 4:17 ` Daniel Jacobowitz
2010-02-08 5:16 ` H.J. Lu
2010-02-08 14:14 ` Daniel Jacobowitz
2010-02-08 14:56 ` H.J. Lu
2010-02-08 18:56 ` H.J. Lu
2010-02-08 18:55 ` PATCH: Cache types from target description H.J. Lu
2010-02-09 15:45 ` H.J. Lu
2010-02-09 18:47 ` Eli Zaretskii
2010-02-09 18:56 ` H.J. Lu
2010-02-10 18:38 ` Daniel Jacobowitz
2010-02-10 20:54 ` Mark Kettenis
2010-02-10 21:01 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100210210135.GY9493@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox