From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Nathan Sidwell" <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org, "Daniel Jacobowitz" <dan@codesourcery.com>
Subject: Re: add vector container type
Date: Mon, 10 Jul 2006 11:54:00 -0000 [thread overview]
Message-ID: <24259.192.87.1.22.1152532444.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <44B2273D.9030906@codesourcery.com>
> The brief outline of this API is that it allows you to define variable
> length
> vectors of scalars, pointers or objects, and then have type-safe accessor
> and
> manipulator functions. GCC has been using this for about 2 years now.
>
> We (CSL) are using this API for some upcoming patches implementing the
> flash
> programming model that has previously been discussed here.
>
> ok?
Nathan, can you give a motivation why we need this in GDB? Just the fact
that GCC uses it and CSL developed some stuff that's based on this, is
hardly enough to justify introducing yet another API to do memory
allocation in GDB. Why are the existing interfaces not good enough for
implementing the flash programming stuff? If this interface is better,
are we going to convert other bits of GDB to use these interfaces?
Could you provide a few examples of how this would be used?
Oh, and Eli will want you to write a paragraph on how to use this in
gdbint.tex.
Mark
next prev parent reply other threads:[~2006-07-10 11:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 10:09 Nathan Sidwell
2006-07-10 11:54 ` Mark Kettenis [this message]
2006-07-10 12:54 ` Daniel Jacobowitz
2006-07-10 19:59 ` Eli Zaretskii
2006-07-13 18:29 ` Nathan Sidwell
2006-07-13 19:25 ` Eli Zaretskii
2006-07-14 16:23 ` Nathan Sidwell
2006-07-14 19:31 ` Eli Zaretskii
2006-07-17 15:09 ` Nathan Sidwell
2006-07-17 18:07 ` Mark Kettenis
2006-07-17 18:15 ` Daniel Jacobowitz
2006-07-11 18:17 ` Jim Blandy
2006-07-11 18:19 ` Nathan Sidwell
2006-08-15 19:42 ` Daniel Jacobowitz
2006-09-21 13:48 ` Daniel Jacobowitz
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=24259.192.87.1.22.1152532444.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=nathan@codesourcery.com \
/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