From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [2/3] RFC: merge symbol "ops" and "aclass" fields
Date: Wed, 20 Mar 2013 18:33:00 -0000 [thread overview]
Message-ID: <87a9px9b70.fsf@fleche.redhat.com> (raw)
In-Reply-To: <874ngd4ten.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 14 Mar 2013 14:29:20 -0600")
Tom> I never fully understood the plan to merge the "ops" and "aclass" fields
Tom> of struct symbol until I stumbled across PR 8421, which explains the
Tom> idea in a bit more detail than the FIXME comment in symtab.h.
Tom> This patch implements the idea outlined there. We drop the "ops" field
Tom> entirely and replace "aclass" with "aclass_index" (the renaming makes it
Tom> obvious that there is a change).
Tom> Here is a version of this patch which incorporates Jan's various
Tom> changes.
I'm checking this in now.
I rebased and re-regtested it, this time on x86-64 Fedora 18.
Tom
prev parent reply other threads:[~2013-03-20 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 16:09 Tom Tromey
2013-02-03 9:06 ` Jan Kratochvil
2013-02-06 15:40 ` Tom Tromey
2013-02-06 15:52 ` Jan Kratochvil
2013-02-07 18:24 ` Jan Kratochvil
2013-02-03 9:20 ` Jan Kratochvil
2013-02-04 16:44 ` Tom Tromey
2013-03-14 20:29 ` Tom Tromey
2013-03-20 18:33 ` Tom Tromey [this message]
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=87a9px9b70.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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