From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch 1/2] Code cleanup: New symbol_filename_ftype
Date: Fri, 10 Jun 2011 20:29:00 -0000 [thread overview]
Message-ID: <20110610202912.GA31746@host1.jankratochvil.net> (raw)
Hi,
no code change, either I could use filename + fullname names everywhere or
- I used - the typedef where one can jump to.
I will check it in less than a week.
Thanks,
Jan
gdb/
2011-06-10 Jan Kratochvil <jan.kratochvil@redhat.com>
Code cleanup.
* dwarf2read.c (dw2_map_symbol_filenames): Use symbol_filename_ftype
for fun.
* psymtab.c (map_symbol_filenames_psymtab)
(map_partial_symbol_filenames): Likewise.
* psymtab.h: Include symfile.h.
(map_partial_symbol_filenames): Use symbol_filename_ftype for fun.
* symfile.h (symbol_filename_ftype): New.
(struct quick_symbol_functions): Use symbol_filename_ftype for fun of
map_symbol_filenames, clarify more the naming in comment.
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -2720,8 +2720,7 @@ dw2_find_pc_sect_symtab (struct objfile *objfile,
}
static void
-dw2_map_symbol_filenames (struct objfile *objfile,
- void (*fun) (const char *, const char *, void *),
+dw2_map_symbol_filenames (struct objfile *objfile, symbol_filename_ftype *fun,
void *data)
{
int i;
--- a/gdb/psymtab.c
+++ b/gdb/psymtab.c
@@ -1082,9 +1082,7 @@ read_psymtabs_with_filename (struct objfile *objfile, const char *filename)
static void
map_symbol_filenames_psymtab (struct objfile *objfile,
- void (*fun) (const char *, const char *,
- void *),
- void *data)
+ symbol_filename_ftype *fun, void *data)
{
struct partial_symtab *ps;
@@ -1917,9 +1915,7 @@ expand_partial_symbol_names (int (*fun) (const char *, void *), void *data)
}
void
-map_partial_symbol_filenames (void (*fun) (const char *, const char *,
- void *),
- void *data)
+map_partial_symbol_filenames (symbol_filename_ftype *fun, void *data)
{
struct objfile *objfile;
--- a/gdb/psymtab.h
+++ b/gdb/psymtab.h
@@ -20,6 +20,8 @@
#ifndef PSYMTAB_H
#define PSYMTAB_H
+#include "symfile.h"
+
/* A bcache for partial symbols. */
struct psymbol_bcache;
@@ -31,9 +33,7 @@ extern struct bcache *psymbol_bcache_get_bcache (struct psymbol_bcache *);
void expand_partial_symbol_names (int (*fun) (const char *, void *),
void *data);
-void map_partial_symbol_filenames (void (*) (const char *, const char *,
- void *),
- void *);
+void map_partial_symbol_filenames (symbol_filename_ftype *fun, void *data);
extern const struct quick_symbol_functions psym_functions;
--- a/gdb/symfile.h
+++ b/gdb/symfile.h
@@ -116,6 +116,11 @@ struct symfile_segment_data
int *segment_info;
};
+/* Callback for quick_symbol_functions->map_symbol_filenames. */
+
+typedef void (symbol_filename_ftype) (const char *filename,
+ const char *fullname, void *data);
+
/* The "quick" symbol functions exist so that symbol readers can
avoiding an initial read of all the symbols. For example, symbol
readers might choose to use the "partial symbol table" utilities,
@@ -283,12 +288,10 @@ struct quick_symbol_functions
int warn_if_readin);
/* Call a callback for every file defined in OBJFILE whose symtab is
- not already read in. FUN is the callback. It is passed the file's name,
- the file's full name, and the DATA passed to this function. */
+ not already read in. FUN is the callback. It is passed the file's
+ FILENAME, the file's FULLNAME, and the DATA passed to this function. */
void (*map_symbol_filenames) (struct objfile *objfile,
- void (*fun) (const char *, const char *,
- void *),
- void *data);
+ symbol_filename_ftype *fun, void *data);
};
/* Structure to keep track of symbol reading functions for various
next reply other threads:[~2011-06-10 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 20:29 Jan Kratochvil [this message]
2011-06-10 20:55 ` Tom Tromey
2011-06-10 21:58 ` Jan Kratochvil
2011-06-10 21:24 ` 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=20110610202912.GA31746@host1.jankratochvil.net \
--to=jan.kratochvil@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