Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org,
	Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Subject: Re: [PING] [RFC/Windows] Remember last tlb type for re-use in windows_get_tlb_type
Date: Fri, 30 Apr 2010 14:53:00 -0000	[thread overview]
Message-ID: <20100430145338.GA11512@ednor.casa.cgf.cx> (raw)
In-Reply-To: <002401cae7ea$ba4b48e0$2ee1daa0$@muller@ics-cnrs.unistra.fr>

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?

cgf
>Pierre
>
>> -----Message d'origine-----
>> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
>> owner@sourceware.org] De la part de Pierre Muller
>> Envoy??: Monday, April 19, 2010 11:00 AM
>> ??: gdb-patches@sourceware.org
>> Objet?: [RFC/Windows] Remember last tlb type for re-use in
>> windows_get_tlb_type
>> 
>>   Each time, you examine the convenience variable
>> $_tlb on Windows executable
>> the function windows_get_tlb_type is called
>> and creates a new type.
>> 
>>   I copied this behavior from the internal variable _siginfo,
>> but I think that it is a big waste of time and memory to
>> regenerate it each time.
>>   Nevertheless, with multi-target GDB, you can possibly create
>> a type of windows-32 bit another for windows 64-bit
>> or even one for windows-CE.
>>   Thus I remember the last gdbarch passed
>> and return the remember type only if gdbarch did not change,
>> which is most of the time.
>> 
>>   I do not know if those kind of patches
>> are regarded as useful.
>> 
>> Comments welcome.
>> 
>> 
>> Pierre Muller
>> 
>> 2010-04-19  Pierre Muller  <muller@ics.u-strasbg.fr>
>> 
>> 	* windows-tdep.c (windows_get_tlb_type): Remember
>> 	last GDBARCH and created type for re-use.
>> 
>> Index: windows-tdep.c
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/windows-tdep.c,v
>> retrieving revision 1.6
>> diff -u -p -r1.6 windows-tdep.c
>> --- windows-tdep.c	16 Apr 2010 07:49:35 -0000	1.6
>> +++ windows-tdep.c	19 Apr 2010 08:45:27 -0000
>> @@ -97,12 +97,18 @@ static int maint_display_all_tib = 0;
>>  static struct type *
>>  windows_get_tlb_type (struct gdbarch *gdbarch)
>>  {
>> +  static struct gdbarch *last_gdbarch = NULL;
>> +  static struct type *last_tlb_type = NULL;
>>    struct type *dword_ptr_type, *dword32_type, *void_ptr_type;
>>    struct type *peb_ldr_type, *peb_ldr_ptr_type;
>>    struct type *peb_type, *peb_ptr_type, *list_type, *list_ptr_type;
>>    struct type *module_list_ptr_type;
>>    struct type *tib_type, *seh_type, *tib_ptr_type, *seh_ptr_type;
>> 
>> +  /* Do not rebuild type if same gdbarch as last time.  */
>> +  if (last_tlb_type && last_gdbarch == gdbarch)
>> +    return last_tlb_type;
>> +
>>    dword_ptr_type = arch_integer_type (gdbarch, gdbarch_ptr_bit
>> (gdbarch),
>>  				 1, "DWORD_PTR");
>>    dword32_type = arch_integer_type (gdbarch, 32,
>> @@ -210,6 +216,9 @@ windows_get_tlb_type (struct gdbarch *gd
>>  			    TYPE_LENGTH (void_ptr_type), NULL);
>>    TYPE_TARGET_TYPE (tib_ptr_type) = tib_type;
>> 
>> +  last_tlb_type = tib_ptr_type;
>> +  last_gdbarch = gdbarch;
>> +
>>    return tib_ptr_type;
>>  }
>> 
>
>
>


  reply	other threads:[~2010-04-30 14:53 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 [this message]
2010-04-30 15:06     ` Pierre Muller
     [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=20100430145338.GA11512@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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