Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: "Nick Roberts" <nickrob@snap.net.nz>,  gdb-patches@sources.redhat.com
Subject: Re: [PATCH:MI] Return a subset of a variable object's children
Date: Thu, 01 May 2008 15:56:00 -0000	[thread overview]
Message-ID: <200805011955.54191.vladimir@codesourcery.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA042910B7@ecamlmw720.eamcs.ericsson.se>

On Wednesday 30 April 2008 18:21:03 Marc Khouzam wrote:
> > > > > > but only actually create the children that have been requested by the
> > > > > > user.  I'm not sure how much efficiency there is by allocating the
> > > > > > memory before hand?  Also, is there no way to grow the vector by more
> > > > > > than a single point at a time?
> > > > > 
> > > > > Like resize with STL vectors?  I'm not aware of one.
> > > > 
> > > > VEC_safe_grow
> > > 
> > > OK, I didn't know about that.  Why not use it instead of VEC_safe_push in the
> > > construct above?
> > 
> > Well, it happens not to initialize the data, so some changes in further logic will
> > be required. Until now, it was not a performance issue.
> 
> My concern about
> 
>   while (VEC_length (varobj_p, var->children) < var->num_children)
>     VEC_safe_push (varobj_p, var->children, NULL);
> 
> is that the vector may be reallocated multiple times.

As soon as we're into big-O here, we still get amortized linear time.

> How about something like this (assuming quick_push does what I think it does)
> 
>   var->children = VEC_alloc(varobj_p, var->num_children);
>   for (i=0; i<var->num_children; i++)
>     VEC_quick_push (varobj_p, var->children, NULL);
> 
> Same loop, but it avoids having to reallocate the vector.

Yes, it's a bit more efficient.

- Volodya


  reply	other threads:[~2008-05-01 15:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 15:34 Nick Roberts
2008-04-29 15:58 ` Marc Khouzam
2008-04-30  7:02   ` Nick Roberts
2008-04-30  9:20     ` Vladimir Prus
2008-04-30  9:25       ` Nick Roberts
2008-04-30  9:39         ` Vladimir Prus
2008-04-30 16:29           ` Marc Khouzam
2008-05-01 15:56             ` Vladimir Prus [this message]
2008-05-01 17:29               ` Marc Khouzam
2008-05-01 12:15           ` Nick Roberts
2008-05-10 14:45             ` Nick Roberts
2008-05-28 19:15               ` Vladimir Prus
2008-05-29 12:01                 ` Nick Roberts
2008-04-30 16:22         ` Marc Khouzam
2008-05-01 15:54           ` Vladimir Prus
2008-05-01 18:14             ` Marc Khouzam
2008-05-01 18:40               ` Vladimir Prus
2008-05-01 20:49                 ` Daniel Jacobowitz
2008-05-01 23:38                   ` Nick Roberts
2008-05-02  0:58                 ` Marc Khouzam
2008-05-11 17:45                   ` Vladimir Prus
2008-04-30 10:47       ` André Pönitz
2008-04-30 12:20         ` Vladimir Prus
2008-04-30 12:53           ` André Pönitz
2008-04-30 13:11             ` Vladimir Prus
2008-04-30 12:44         ` Nick Roberts
     [not found]           ` <200804301244.55116.apoenitz@trolltech.com>
2008-04-30 13:16             ` André Pönitz
2008-05-01  6:27               ` Nick Roberts
2008-05-05 11:46                 ` André Pönitz
2008-04-30 14:59     ` Marc Khouzam
2008-05-01 12:06       ` Nick Roberts
2008-05-01 14:22         ` Marc Khouzam
2008-05-01 20:41     ` Daniel Jacobowitz
2008-04-30  8:59 ` Vladimir Prus

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=200805011955.54191.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=marc.khouzam@ericsson.com \
    --cc=nickrob@snap.net.nz \
    /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