public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tsukasa OI <a4lg@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] sim/erc32: Insert void parameter Date: Sat, 29 Oct 2022 08:14:55 +0000 (GMT) [thread overview] Message-ID: <20221029081455.69BD03858C78@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=dc4e697f2fec232cecfd1d162365ce836c785369 commit dc4e697f2fec232cecfd1d162365ce836c785369 Author: Tsukasa OI <research_trasio@irq.a4lg.com> Date: Sat Sep 24 09:16:57 2022 +0000 sim/erc32: Insert void parameter Clang generates a warning if there is a function declaration/definition with zero arguments. Such declarations/definitions without a prototype (an argument list) are deprecated forms of indefinite arguments ("-Wdeprecated-non-prototype"). On the default configuration, it causes a build failure (unless "--disable-werror" is specified). This commit replaces () with (void) to avoid this warning. Diff: --- sim/erc32/func.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sim/erc32/func.c b/sim/erc32/func.c index 4d1942065b8..af92c9f7d48 100644 --- a/sim/erc32/func.c +++ b/sim/erc32/func.c @@ -298,7 +298,7 @@ disp_reg(struct pstate *sregs, char *reg) #ifdef ERRINJ void -errinj() +errinj (void) { int err; @@ -322,7 +322,7 @@ errinj() } void -errinjstart() +errinjstart (void) { if (errper) event(errinj, 0, (random()%errper)); } @@ -855,7 +855,7 @@ event(void (*cfunc) (), int32_t arg, uint64_t delta) #if 0 /* apparently not used */ void -stop_event() +stop_event(void) { } #endif
reply other threads:[~2022-10-29 8:14 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=20221029081455.69BD03858C78@sourceware.org \ --to=a4lg@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).