From: Keith Seitz <keiths@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Special casing dtors?
Date: Fri, 24 Apr 2009 17:54:00 -0000 [thread overview]
Message-ID: <49F1FCB5.3080404@redhat.com> (raw)
In-Reply-To: <m37i1apoyr.fsf@fleche.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
Tom Tromey wrote:
> I re-read this whole thread this evening, and as far as I can tell,
> the original cleanup patch is ok. Early in the thread, Keith said
> he'd send a new one that also removed get_destructor_fn_field.
> Keith, could you do that?
I've attached it.
Keith
ChangeLog
2009-04-24 Keith Seitz <keiths@redhat.com>
* gdbtypes.h (get_destructor_fn_field): Remove. No longer needed.
* gdbtypes.c (get_destructor_fn_field): Likewise.
[-- Attachment #2: remove-get_dtor_fn_field.patch --]
[-- Type: text/plain, Size: 1620 bytes --]
Index: gdbtypes.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtypes.c,v
retrieving revision 1.162
diff -u -p -r1.162 gdbtypes.c
--- gdbtypes.c 10 Apr 2009 03:36:32 -0000 1.162
+++ gdbtypes.c 24 Apr 2009 17:50:53 -0000
@@ -1334,34 +1334,6 @@ get_vptr_fieldno (struct type *type, str
}
}
-/* Find the method and field indices for the destructor in class type T.
- Return 1 if the destructor was found, otherwise, return 0. */
-
-int
-get_destructor_fn_field (struct type *t,
- int *method_indexp,
- int *field_indexp)
-{
- int i;
-
- for (i = 0; i < TYPE_NFN_FIELDS (t); i++)
- {
- int j;
- struct fn_field *f = TYPE_FN_FIELDLIST1 (t, i);
-
- for (j = 0; j < TYPE_FN_FIELDLIST_LENGTH (t, i); j++)
- {
- if (is_destructor_name (TYPE_FN_FIELD_PHYSNAME (f, j)) != 0)
- {
- *method_indexp = i;
- *field_indexp = j;
- return 1;
- }
- }
- }
- return 0;
-}
-
static void
stub_noname_complaint (void)
{
Index: gdbtypes.h
===================================================================
RCS file: /cvs/src/src/gdb/gdbtypes.h,v
retrieving revision 1.100
diff -u -p -r1.100 gdbtypes.h
--- gdbtypes.h 26 Mar 2009 01:27:45 -0000 1.100
+++ gdbtypes.h 24 Apr 2009 17:50:53 -0000
@@ -1201,8 +1201,6 @@ extern struct type *lookup_template_type
extern int get_vptr_fieldno (struct type *, struct type **);
-extern int get_destructor_fn_field (struct type *, int *, int *);
-
extern int get_discrete_bounds (struct type *, LONGEST *, LONGEST *);
extern int is_ancestor (struct type *, struct type *);
next prev parent reply other threads:[~2009-04-24 17:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 22:39 Keith Seitz
2009-03-26 22:07 ` Tom Tromey
2009-03-26 22:39 ` Stan Shebs
2009-03-27 2:35 ` Daniel Jacobowitz
2009-03-27 8:07 ` Keith Seitz
2009-03-27 15:06 ` Pedro Alves
2009-03-27 15:41 ` Joel Brobecker
2009-03-27 17:19 ` Keith Seitz
2009-03-27 17:49 ` Pedro Alves
2009-03-27 19:05 ` Keith Seitz
2009-03-27 19:22 ` Pedro Alves
2009-03-28 0:56 ` Keith Seitz
2009-03-28 8:56 ` Keith Seitz
2009-03-30 21:46 ` Pedro Alves
2009-04-01 23:48 ` Keith Seitz
2009-04-02 3:17 ` Daniel Jacobowitz
2009-04-02 16:25 ` Keith Seitz
2009-04-02 16:32 ` Daniel Jacobowitz
2009-04-02 8:27 ` Mark Kettenis
2009-04-07 20:54 ` Pedro Alves
2009-04-07 21:26 ` Keith Seitz
2009-04-24 6:06 ` Tom Tromey
2009-04-24 17:54 ` Keith Seitz [this message]
2009-04-24 22:49 ` Tom Tromey
2009-06-16 18:41 ` Keith Seitz
2009-03-28 21:19 ` 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=49F1FCB5.3080404@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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