pspp-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v0.7.9-222-g4d24c


From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v0.7.9-222-g4d24ceb
Date: Sat, 05 May 2012 17:02:43 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU PSPP".

The branch, master has been updated
       via  4d24ceb787e6e53bd76ef9006c7f73e975dda140 (commit)
      from  78616e13d5fed640d83c0b5b19507129c4c21690 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4d24ceb787e6e53bd76ef9006c7f73e975dda140
Author: Ben Pfaff <address@hidden>
Date:   Fri May 4 21:30:49 2012 -0700

    configure.ac: Link PSPPIRE explicitly against gthread.
    
    Seems to be required on OpenSUSE.
    
    PSPPIRE does not make explicit use of threads, but it does use
    GTimer.  Thus, it calls g_thread_init() because of the following
    note in the documentation for GTimer:
    
        GTimer uses a higher-quality clock when thread support is
        available.  Therefore, calling g_thread_init() while timers
        are running may lead to unreliable results.  It is best to
        call g_thread_init() before starting any timers, if you are
        using threads at all.
    
    Separately, the documentation for threads in Glib says:
    
        Calling g_thread_init() with a NULL argument is somewhat more
        relaxed.  You may call any other glib functions in the main
        thread before g_thread_init() as long as g_thread_init() is
        not called from a glib callback, or with any locks held.
        However, many libraries above glib does not support late
        initialization of threads, so doing this should be avoided if
        possible.
    
        Please note that since version 2.24 the GObject
        initialization function g_type_init() initializes threads
        (with a NULL argument), so most applications, including those
        using Gtk+ will run with threads enabled.  If you want a
        special thread implementation, make sure you call
        g_thread_init() before g_type_init() is called.
    
    Taken together, it seems to imply that PSPPIRE should call
    g_thread_init() before g_timer_new(), or the timer might be
    unreliable because Glib would call it later for us.  But the
    documentation doesn't seem entirely clear.
    
    Reported by Mindaugas.
    Bug #36396.

-----------------------------------------------------------------------

Summary of changes:
 configure.ac           |    3 +++
 src/ui/gui/automake.mk |    1 +
 2 files changed, 4 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
GNU PSPP



reply via email to

[Prev in Thread] Current Thread [Next in Thread]