From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com,
Elena Zannoni <ezannoni@redhat.com>,
Fernando Nasser <fnasser@redhat.com>
Subject: Re: [rfa] linespec.c: collect_methods
Date: Sun, 02 Mar 2003 22:27:00 -0000 [thread overview]
Message-ID: <15970.34377.260115.454270@localhost.redhat.com> (raw)
In-Reply-To: <ro1heaoj9v2.fsf@jackfruit.Stanford.EDU>
David Carlton writes:
> The latest linespec patch. It extracts some code from find_method
> into a new function collect_methods. It doesn't change the extracted
> code.
>
> And yes, I do realize that having functions with the similar names
> find_methods, find_method, and collect_methods is confusing (not to
> mention having a function with a similar functionality but a different
> name, namely decode_line_2); I'll rename existing functions to clarify
> their roles once I'm done with extracting funcitons in this code.
> (find_methods and decode_line_2 were around before I started this
> project.)
>
> Tested on i686-pc-linux-gnu/GCC3.1/DWARF-2; OK to apply?
>
yes
elena
> David Carlton
> carlton@math.stanford.edu
>
> 2003-02-28 David Carlton <carlton@math.stanford.edu>
>
> * linespec.c (find_method): Extract code into collect_methods.
> (collect_methods): New.
>
> Index: linespec.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/linespec.c,v
> retrieving revision 1.44
> diff -u -p -r1.44 linespec.c
> --- linespec.c 28 Feb 2003 17:21:16 -0000 1.44
> +++ linespec.c 28 Feb 2003 22:38:34 -0000
> @@ -64,6 +64,9 @@ static struct symtabs_and_lines find_met
> struct type *t,
> struct symbol *sym_class);
>
> +static int collect_methods (char *copy, struct type *t,
> + struct symbol **sym_arr);
> +
> static NORETURN void cplusplus_error (const char *name,
> const char *fmt, ...)
> ATTR_NORETURN ATTR_FORMAT (printf, 2, 3);
> @@ -1135,29 +1138,15 @@ find_method (int funfirstline, char ***c
> {
> struct symtabs_and_lines values;
> struct symbol *sym = 0;
> - int i1 = 0; /* Counter for the symbol array. */
> + int i1; /* Counter for the symbol array. */
> struct symbol **sym_arr = alloca (total_number_of_methods (t)
> * sizeof (struct symbol *));
>
> - if (destructor_name_p (copy, t))
> - {
> - /* Destructors are a special case. */
> - int m_index, f_index;
> + /* Find all methods with a matching name, and put them in
> + sym_arr. */
>
> - if (get_destructor_fn_field (t, &m_index, &f_index))
> - {
> - struct fn_field *f = TYPE_FN_FIELDLIST1 (t, m_index);
> + i1 = collect_methods (copy, t, sym_arr);
>
> - sym_arr[i1] =
> - lookup_symbol (TYPE_FN_FIELD_PHYSNAME (f, f_index),
> - NULL, VAR_NAMESPACE, (int *) NULL,
> - (struct symtab **) NULL);
> - if (sym_arr[i1])
> - i1++;
> - }
> - }
> - else
> - i1 = find_methods (t, copy, sym_arr);
> if (i1 == 1)
> {
> /* There is exactly one field with that name. */
> @@ -1204,6 +1193,38 @@ find_method (int funfirstline, char ***c
> "the class %s does not have any method named %s\n",
> SYMBOL_PRINT_NAME (sym_class), tmp);
> }
> +}
> +
> +/* Find all methods named COPY in the class whose type is T, and put
> + them in SYM_ARR. Return the number of methods found. */
> +
> +static int
> +collect_methods (char *copy, struct type *t,
> + struct symbol **sym_arr)
> +{
> + int i1 = 0; /* Counter for the symbol array. */
> +
> + if (destructor_name_p (copy, t))
> + {
> + /* Destructors are a special case. */
> + int m_index, f_index;
> +
> + if (get_destructor_fn_field (t, &m_index, &f_index))
> + {
> + struct fn_field *f = TYPE_FN_FIELDLIST1 (t, m_index);
> +
> + sym_arr[i1] =
> + lookup_symbol (TYPE_FN_FIELD_PHYSNAME (f, f_index),
> + NULL, VAR_NAMESPACE, (int *) NULL,
> + (struct symtab **) NULL);
> + if (sym_arr[i1])
> + i1++;
> + }
> + }
> + else
> + i1 = find_methods (t, copy, sym_arr);
> +
> + return i1;
> }
>
> \f
next prev parent reply other threads:[~2003-03-02 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 22:53 David Carlton
2003-03-02 22:27 ` Elena Zannoni [this message]
2003-03-03 17:22 ` David Carlton
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=15970.34377.260115.454270@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=fnasser@redhat.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