Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jerome Guitton <guitton@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com,
		Francois Rigault <francois.rigault@amadeus.com>
Subject: Re: [Bug symtab/8367] [RFA]  performance improvement of 	lookup_partial_symtab
Date: Wed, 29 Apr 2009 08:54:00 -0000	[thread overview]
Message-ID: <20090429085350.GW37172@adacore.com> (raw)
In-Reply-To: <20090428195726.GA31821@adacore.com>

Joel Brobecker (brobecker@adacore.com):

> > > 2009-01-14  Jerome Guitton  <guitton@adacore.com>
> > > 
> > > 	* symtab.c (lookup_partial_symtab): When looking up an absolute path
> > > 	in the partial symtabs, compare the base names before checking the
> > > 	full names.
> 
> We're only 3.5 months late reviewing this patch :-(... This looks OK
> to me. I verified that this cannot create behavior changes due to
> find_and_open_source returning a fullname with a different basename
> (for instance if the source file was actually a link to another source
> file): openp only canonicalizes the directory portion of the fullname.
> 
> So I think this is reasonable. Please go ahead and commit.


There has been an alternative patch for the same problem, submitted here:

http://sourceware.org/ml/gdb-patches/2009-03/msg00309.html

François' patch should handle one more problem (files can be the same
even if basenames differs). So I prefer his approach. I think there's
still some paperwork to be done before we can merge his changes into
GDB (copyright assignment), but I guess that it will happen at some
point in the future. If not, I will modify my patch to take the link
problem into account.



  reply	other threads:[~2009-04-29  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 17:46 Jerome Guitton
2009-01-15  9:45 ` Jerome Guitton
2009-04-28 19:57   ` Joel Brobecker
2009-04-29  8:54     ` Jerome Guitton [this message]
2009-04-28 20:00   ` Joel Brobecker

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=20090429085350.GW37172@adacore.com \
    --to=guitton@adacore.com \
    --cc=brobecker@adacore.com \
    --cc=francois.rigault@amadeus.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