From: Anthony Liguori <anthony@codemonkey.ws>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] g_thread_init users: don't call it if glib >= 2.31
Date: Tue, 20 Dec 2011 16:17:01 -0600 [thread overview]
Message-ID: <4EF1095D.1070508@codemonkey.ws> (raw)
In-Reply-To: <1324381264-5959-1-git-send-email-alevy@redhat.com>
On 12/20/2011 05:41 AM, Alon Levy wrote:
> since commit f9b29ca03 included in release 2.31 (docs below say 2.32 but
> that is not correct) and onwards g_thread_init is deprecated and calling
> it is not required:
>
> http://developer.gnome.org/glib/unstable/glib-Deprecated-Thread-APIs.html#g-thread-init
>
> g_thread_init has been deprecated since version 2.32 and should not be
> used in newly-written code. This function is no longer necessary. The
> GLib threading system is automatically initialized at the start of your
> program.
>
> Fixes bulid failure when warnings are treated as errors on fedora 17.
>
> I only tested the change to vl.c, and copy pasted to the two other
> locations (couldn't decide if a wrapper for calling g_thread_init is
> uglier).
>
> Signed-off-by: Alon Levy<alevy@redhat.com>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> coroutine-gthread.c | 5 +++++
> trace/simple.c | 5 +++++
> vl.c | 5 +++++
> 3 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/coroutine-gthread.c b/coroutine-gthread.c
> index fdea27a..662801b 100644
> --- a/coroutine-gthread.c
> +++ b/coroutine-gthread.c
> @@ -36,7 +36,12 @@ static GStaticPrivate coroutine_key = G_STATIC_PRIVATE_INIT;
> static void __attribute__((constructor)) coroutine_init(void)
> {
> if (!g_thread_supported()) {
> +#if !GLIB_CHECK_VERSION(2, 31, 0)
> g_thread_init(NULL);
> +#else
> + fprintf(stderr, "glib threading failed to initialize.\n");
> + exit(1);
> +#endif
> }
>
> coroutine_cond = g_cond_new();
> diff --git a/trace/simple.c b/trace/simple.c
> index 6339152..bbc9930 100644
> --- a/trace/simple.c
> +++ b/trace/simple.c
> @@ -376,7 +376,12 @@ bool trace_backend_init(const char *events, const char *file)
> GThread *thread;
>
> if (!g_thread_supported()) {
> +#if !GLIB_CHECK_VERSION(2, 31, 0)
> g_thread_init(NULL);
> +#else
> + fprintf(stderr, "glib threading failed to initialize.\n");
> + exit(1);
> +#endif
> }
>
> trace_available_cond = g_cond_new();
> diff --git a/vl.c b/vl.c
> index da69f94..06c9c94 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -2176,7 +2176,12 @@ int main(int argc, char **argv, char **envp)
>
> g_mem_set_vtable(&mem_trace);
> if (!g_thread_supported()) {
> +#if !GLIB_CHECK_VERSION(2, 31, 0)
> g_thread_init(NULL);
> +#else
> + fprintf(stderr, "glib threading failed to initialize.\n");
> + exit(1);
> +#endif
> }
>
> runstate_init();
next prev parent reply other threads:[~2011-12-20 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 11:41 [Qemu-devel] [PATCH] g_thread_init users: don't call it if glib >= 2.31 Alon Levy
2011-12-20 22:17 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-20 14:15 Alon Levy
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=4EF1095D.1070508@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).