public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Two minor changes in ctfread.c Date: Tue, 28 Jan 2020 02:42:00 -0000 [thread overview] Message-ID: <168f8c6ba008bed9fcc2fe7098416f608e4419af@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 168f8c6ba008bed9fcc2fe7098416f608e4419af *** commit 168f8c6ba008bed9fcc2fe7098416f608e4419af Author: Tom Tromey <tom@tromey.com> AuthorDate: Sun Jan 26 18:43:17 2020 -0700 Commit: Tom Tromey <tom@tromey.com> CommitDate: Sun Jan 26 18:44:41 2020 -0700 Two minor changes in ctfread.c I noticed a couple of minor issues in ctfread.c, both fixed by this patch: * ctf_fp_info was not indented properly; and * _initialize_ctfread is no longer needed gdb/ChangeLog 2020-01-26 Tom Tromey <tom@tromey.com> * ctfread.c (struct ctf_fp_info): Reindent. (_initialize_ctfread): Remove. Change-Id: I72707b74bc59e6e426b3a7bc8843d96c0d786f1e diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 77e52f3c5a..8b6da62bd4 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2020-01-26 Tom Tromey <tom@tromey.com> + + * ctfread.c (struct ctf_fp_info): Reindent. + (_initialize_ctfread): Remove. + 2020-01-26 Tom Tromey <tom@tromey.com> * psymtab.c (partial_map_expand_apply) diff --git a/gdb/ctfread.c b/gdb/ctfread.c index d363ce6a11..844ab7b9db 100644 --- a/gdb/ctfread.c +++ b/gdb/ctfread.c @@ -88,9 +88,9 @@ static const struct objfile_key<htab, htab_deleter> ctf_tid_key; struct ctf_fp_info { - explicit ctf_fp_info (ctf_file_t *cfp) : fp (cfp) {} - ~ctf_fp_info (); - ctf_file_t *fp; + explicit ctf_fp_info (ctf_file_t *cfp) : fp (cfp) {} + ~ctf_fp_info (); + ctf_file_t *fp; }; /* Cleanup function for the ctf_file_key data. */ @@ -1485,9 +1485,3 @@ elfctf_build_psymtabs (struct objfile *of) scan_partial_symbols (fp, of); } - -void _initialize_ctfread (); -void -_initialize_ctfread () -{ -}
next reply other threads:[~2020-01-28 2:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-28 2:42 gdb-buildbot [this message] 2020-01-28 3:15 ` Failures on Fedora-i686, branch master gdb-buildbot 2020-01-28 3:31 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot 2020-01-28 3:49 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-01-28 4:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-01-28 4:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-01-28 6:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot 2020-01-28 7:03 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot 2020-01-28 8:17 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
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=168f8c6ba008bed9fcc2fe7098416f608e4419af@gdb-build \ --to=gdb-buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).