From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: RE: [PING] [RFC/Windows] Remember last tlb type for re-use in windows_get_tlb_type
Date: Fri, 30 Apr 2010 15:06:00 -0000 [thread overview]
Message-ID: <000601cae876$a1459f80$e3d0de80$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100430145338.GA11512@ednor.casa.cgf.cx>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Christopher Faylor
> Envoyé : Friday, April 30, 2010 4:54 PM
> À : gdb-patches@sourceware.org; Pierre Muller
> Objet : Re: [PING] [RFC/Windows] Remember last tlb type for re-use in
> windows_get_tlb_type
>
> On Fri, Apr 30, 2010 at 12:24:26AM +0200, Pierre Muller wrote:
> >Nobody reacted to this:
> >http://sourceware.org/ml/gdb-patches/2010-04/msg00552.html
> >
> >It helps avoid some unnecessary recomputation.
>
> Looks ok but is this computation really so onerous that we need to add
> the extra code?
Each time you dereference $_tlb
you recreate the same bunch of internal types
leaving the other types in the wild...
This looses computation time and memory.
Imagine that you use a long script with
a breakpoint that has commands associated
that print $_tlb.current_seh to check if the current structured exception
handler has changed....
Honestly, I don't know if it can become a big problem,
but I thought it would be better to avoid it.
I first was thinking about removing old values,
but I didn't find a clean way to remove the type and all its
dependents...
Pierre Muller
next prev parent reply other threads:[~2010-04-30 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:59 Pierre Muller
2010-04-29 22:24 ` [PING] " Pierre Muller
2010-04-30 14:53 ` Christopher Faylor
2010-04-30 15:06 ` Pierre Muller [this message]
[not found] ` <2540.9180707813$1272639973@news.gmane.org>
2010-04-30 15:22 ` Tom Tromey
2010-04-30 15:34 ` Christopher Faylor
2010-04-30 15:42 ` Pierre Muller
2010-04-30 16:17 ` Tom Tromey
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='000601cae876$a1459f80$e3d0de80$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
/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