From: John Kacur <jkacur@redhat.com>
To: Josh Cartwright <joshc@ni.com>
Cc: Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH rt-tests 8/9] error: mark fatal, err_exit, err_quit as being noreturn
Date: Wed, 16 Sep 2015 00:31:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.20.1509160030270.13077@riemann.fritz.box> (raw)
In-Reply-To: <0e671c826ca8281e8ad005a9dbc4f553cc816e8d.1441038216.git.joshc@ni.com>
On Mon, 31 Aug 2015, Josh Cartwright wrote:
> These functions never return to their caller. Mark them as such to aide
> in code generation and help out static analysis.
>
> Signed-off-by: Josh Cartwright <joshc@ni.com>
> ---
> src/include/error.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/src/include/error.h b/src/include/error.h
> index ae05a2e..4acff49 100644
> --- a/src/include/error.h
> +++ b/src/include/error.h
> @@ -6,14 +6,14 @@
> #include <stdarg.h>
> #include <string.h>
>
> -void err_exit(int err, char *fmt, ...);
> +void err_exit(int err, char *fmt, ...) __attribute__((noreturn));
> void err_msg(char *fmt, ...);
> void err_msg_n(int err, char *fmt, ...);
> -void err_quit(char *fmt, ...);
> +void err_quit(char *fmt, ...) __attribute__((noreturn));
> void debug(char *fmt, ...);
> void info(char *fmt, ...);
> void warn(char *fmt, ...);
> -void fatal(char *fmt, ...);
> +void fatal(char *fmt, ...) __attribute__((noreturn));
> void err_doit(int err, const char *fmt, va_list ap);
>
> #endif /* __ERROR_H */
> --
> 2.5.0
>
> --
Signed-off-by: John Kacur <jkacur@redhat.com>
next prev parent reply other threads:[~2015-09-15 22:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 16:35 [PATCH rt-tests 0/9] more rt-tests cleanups and a cyclictest feature Josh Cartwright
2015-08-31 16:35 ` [PATCH rt-tests 1/9] cyclictest: consistently make all functions 'static' Josh Cartwright
2015-09-02 13:03 ` John Kacur
2015-08-31 16:35 ` [PATCH rt-tests 2/9] cyclictest: fixup documentation for --priority option Josh Cartwright
2015-09-01 21:03 ` John Kacur
2015-09-01 21:11 ` Josh Cartwright
2015-08-31 16:35 ` [PATCH rt-tests 3/9] cyclictest: drop unnecessary numa_on_and_available() check Josh Cartwright
2015-09-15 21:50 ` John Kacur
2015-09-16 19:47 ` Josh Cartwright
2015-09-17 19:15 ` John Kacur
2015-08-31 16:35 ` [PATCH rt-tests 4/9] signaltest: drop unused tsnorm() Josh Cartwright
2015-09-15 22:00 ` John Kacur
2015-09-16 19:48 ` Josh Cartwright
2015-08-31 16:35 ` [PATCH rt-tests 5/9] cyclictest: use correct type when allocating cpu bitmask size Josh Cartwright
2015-09-15 22:19 ` John Kacur
2015-08-31 16:35 ` [PATCH rt-tests 6/9] cyclictest: drop impossible use_fifo conditional Josh Cartwright
2015-09-15 22:24 ` John Kacur
2015-08-31 16:35 ` [PATCH rt-tests 7/9] cyclictest: fail if use_fifo && thread creation failed Josh Cartwright
2015-09-15 22:25 ` John Kacur
2015-08-31 16:35 ` [PATCH rt-tests 8/9] error: mark fatal, err_exit, err_quit as being noreturn Josh Cartwright
2015-09-15 22:31 ` John Kacur [this message]
2015-08-31 16:35 ` [PATCH rt-tests 9/9] cyclictest: add option for dumping the histogram in a file Josh Cartwright
2015-09-15 23:05 ` John Kacur
2015-09-16 19:56 ` Josh Cartwright
2015-09-17 19:40 ` John Kacur
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=alpine.LFD.2.20.1509160030270.13077@riemann.fritz.box \
--to=jkacur@redhat.com \
--cc=joshc@ni.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@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;
as well as URLs for NNTP newsgroup(s).