From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Replace reread_symbols by load+free calls
Date: Fri, 14 Aug 2009 23:09:00 -0000 [thread overview]
Message-ID: <m3tz0agh3c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090625192120.GA29930@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Thu\, 25 Jun 2009 21\:21\:20 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Sorry about the long delay on this. I try not to just drop threads I'm
involved in, but sometimes I get distracted.
Jan> IMO the whole `struct objfile' should replaced by a new one
Jan> (instead of its in-place patching). Which will probably have
Jan> other dependencies...
Tom> I'm interested to hear your idea and reasoning.
Jan> Sometimes there are differentiations between complete objects
Jan> destructors (objfile_free_data) and in-place object deletions
Jan> (clear_objfile_data); OK did not briefly found more such cases now.
Jan> Expecting it was there for some performance improvements which not
Jan> worth it nowadays.
I misunderstood something you were saying earlier in the thread -- I
thought you were talking about dropping 'struct objfile' itself in favor
of some new datastructure (as opposed to slowly refactoring it). But,
now I understand that you really meant that reread_symbols should be
rewritten.
I realize you pulled this patch from consideration. But, FWIW, I tend
to think it is a good idea, because it ensures that all the hooks and
observers will be run identically in both cases.
Tom
next prev parent reply other threads:[~2009-08-14 22:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 0:12 [patch] Use mmap instead of obstack_alloc for dwarf debug sections Paul Pluzhnikov
2009-05-28 1:16 ` Tom Tromey
2009-05-28 16:57 ` Paul Pluzhnikov
2009-05-30 22:36 ` Tom Tromey
2009-06-11 1:40 ` Paul Pluzhnikov
2009-06-11 1:43 ` Paul Pluzhnikov
2009-06-16 19:19 ` Tom Tromey
2009-06-16 20:43 ` Paul Pluzhnikov
2009-06-16 20:59 ` Tom Tromey
2009-06-16 21:07 ` Paul Pluzhnikov
2009-06-18 9:20 ` Ken Werner
2009-06-18 14:06 ` Paul Pluzhnikov
2009-06-18 14:11 ` Paul Pluzhnikov
2009-06-18 15:02 ` Ken Werner
2009-06-18 16:33 ` Paul Pluzhnikov
2009-06-19 7:10 ` Ken Werner
2009-06-23 15:03 ` [patch] Fix a reread_symbols regression by mmap [Re: [patch] Use mmap instead of obstack_alloc for dwarf debug sections.] Jan Kratochvil
2009-06-23 17:35 ` Paul Pluzhnikov
2009-06-23 18:08 ` Tom Tromey
2009-06-23 18:21 ` Jan Kratochvil
2009-06-23 20:00 ` Tom Tromey
2009-06-25 19:21 ` [patch] Replace reread_symbols by load+free calls Jan Kratochvil
2009-06-25 19:57 ` Pedro Alves
2009-06-25 23:25 ` Jan Kratochvil
2009-08-02 21:04 ` cancelled: " Jan Kratochvil
2009-08-14 23:09 ` Tom Tromey [this message]
2009-08-14 23:12 ` Pedro Alves
2009-08-17 15:41 ` Tom Tromey
2011-12-18 11:54 ` Jan Kratochvil
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=m3tz0agh3c.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jan.kratochvil@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