public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: make throw_perror_with_name static Date: Wed, 8 Jun 2022 19:04:56 +0000 (GMT) [thread overview] Message-ID: <20220608190456.00E0138BE6AE@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=42d77edce1b4d49fed11fc79576ebe359f9b5f7f commit 42d77edce1b4d49fed11fc79576ebe359f9b5f7f Author: Andrew Burgess <aburgess@redhat.com> Date: Tue Jun 7 17:23:42 2022 +0100 gdb: make throw_perror_with_name static The throw_perror_with_name function is not used outside of utils.c right now. And as perror_with_name is just a wrapper around throw_perror_with_name, then any future calls would be to perror_with_name. Lets make throw_perror_with_name static. There should be no user visible changes after this commit. Diff: --- gdb/utils.c | 2 +- gdb/utils.h | 3 --- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/gdb/utils.c b/gdb/utils.c index f9dc4f23431..413a4f4d53b 100644 --- a/gdb/utils.c +++ b/gdb/utils.c @@ -623,7 +623,7 @@ perror_string (const char *prefix) as the file name for which the error was encountered. Use ERRCODE for the thrown exception. Then return to command level. */ -void +static void ATTRIBUTE_NORETURN throw_perror_with_name (enum errors errcode, const char *string) { std::string combined = perror_string (string); diff --git a/gdb/utils.h b/gdb/utils.h index 7e2028580bf..d2acf899ba2 100644 --- a/gdb/utils.h +++ b/gdb/utils.h @@ -296,9 +296,6 @@ extern CORE_ADDR string_to_core_addr (const char *my_string); extern void fprintf_symbol (struct ui_file *, const char *, enum language, int); -extern void throw_perror_with_name (enum errors errcode, const char *string) - ATTRIBUTE_NORETURN; - extern void perror_warning_with_name (const char *string); extern void print_sys_errmsg (const char *, int);
reply other threads:[~2022-06-08 19:04 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220608190456.00E0138BE6AE@sourceware.org \ --to=aburgess@sourceware.org \ --cc=gdb-cvs@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).