Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc[ Opaque bcache
Date: Wed, 10 Jul 2002 15:39:00 -0000	[thread overview]
Message-ID: <3D2CB5F0.7040300@ges.redhat.com> (raw)
In-Reply-To: <20020710222254.GA25885@nevyn.them.org>

> On Wed, Jul 10, 2002 at 06:15:47PM -0400, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> This makes the bcache object opaque.  Testing so far hasn't shown 
>> problems.  I'll look to commit it in a few days.
>> 
>> comments?  Hmm, did I remember to update the makefile ....
> 
> 
> Nope to updating the Makefile, and nope to comments:


  :-)


>> +/* The type used to hold a single bcache string.  The user data is
>> +   stored in d.data.  Since it can be any type, it needs to have the
>> +   same alignment as the most strict alignment of any type on the host
>> +   machine.  I don't know of any really correct way to do this in
>> +   stock ANSI C, so just do it the same way obstack.h does.
>> +
>> +   It would be nicer to have this stuff hidden away in bcache.c, but
>> +   struct objstack contains a struct bcache directly --- not a pointer
>> +   to one --- and then the memory-mapped stuff makes this a real pain.
>> +   We don't strictly need to expose struct bstring, but it's better to
>> +   have it all in one place.  */
> 
> 
> That's not accurate any more.  Other than that, this looks great; and
> it removes a lot of &'s we used to need when accessing a bcache, which
> I quite like.

Hmm, yes, I should clean up the comments I simply cut/paste.

Andrew



  reply	other threads:[~2002-07-10 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 15:22 Andrew Cagney
2002-07-10 15:32 ` Daniel Jacobowitz
2002-07-10 15:39   ` Andrew Cagney [this message]
2002-07-12  8:48     ` Andrew Cagney

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=3D2CB5F0.7040300@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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