luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-01-13 07:56:17 +01:00
Code Issues Packages Projects Releases Wiki Activity
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
29,233 Commits 298 Branches 581 Tags 115 MiB
C 95.3%
Python 2.4%
Meson 1.3%
Objective-C 0.3%
Shell 0.2%
Other 0.5%
94c735a2aa
Go to file
Thomas Haller 94c735a2aa gobject: don't freeze to queue notify event in g_object_notify_by_spec_internal() 
Previously:

- if the object is currently not frozen, we called
  g_object_notify_queue_freeze() once. Afterwards dispatch the event
  directly. This is probably the common case, and requires one
  notify_lock lock.

- if the object is currently frozen, we call
  g_object_notify_queue_freeze(), g_object_notify_queue_add().
  g_object_notify_queue_thaw().
  This required taking the notify_lock three times.

- if the object is currently not frozen and in_init, then we called
  g_object_notify_queue_freeze(), g_object_notify_queue_freeze(),
  g_object_notify_queue_add(). This also required to take
  the lock three times. There is another thaw at the end of
  object initialization.

That was because we first call g_object_notify_queue_freeze() to see
whether we are frozen. And depending on that, queue the event (and thaw
again).

Instead, g_object_notify_queue_add() can do the check and queueing in
one step. There is no need to call a freeze() to (conditionally) enqueue
a notification. Now only one lock is taken in all cases.

Also, g_object_notify_queue_freeze() and g_object_notify_queue_thaw()
both call g_datalist_id_get_data() (which also take a bit lock). As the
thaw is no longer necessary, the second lock is also saved.
2023-12-21 07:26:50 +01:00
.gitlab-ci ci: Build with introspection enabled 2023-12-12 16:58:26 +00:00
.reuse girepository: Add remaining license/copyright SPDX headers 2023-10-25 17:12:25 +01:00
docs docs: Add GIRepository documentation build using gi-docgen 2023-12-12 16:58:04 +00:00
fuzzing Add fuzzing harness for g_utf8_normalize() 2023-04-14 15:50:47 +00:00
gio gio: Use g_task_return_error_literal() where we don't need formatting 2023-12-20 16:14:57 +00:00
girepository build: Ensure gi-visibility.h is built before libgirepository_dep is used 2023-12-19 18:41:02 +00:00
glib GDateTime: Add usec precision API for unix time 2023-12-20 07:48:10 -05:00
gmodule Generate introspection data 2023-10-23 11:26:53 +01:00
gobject gobject: don't freeze to queue notify event in g_object_notify_by_spec_internal() 2023-12-21 07:26:50 +01:00
gthread meson: Add tests for generated pkg-config files 2023-04-17 14:25:52 +02:00
LICENSES girepository: Add remaining license/copyright SPDX headers 2023-10-25 17:12:25 +01:00
m4macros m4macros: drop unused m4 files 2023-07-30 17:03:07 +04:00
po Update Russian translation 2023-11-27 16:26:55 +00:00
subprojects docs: Add initial support for using gi-docgen for docs 2023-10-11 14:01:28 +01:00
tests Convert tests/assert-msg-test* to glib/tests/assert-msg-test* 2022-06-28 11:19:21 +01:00
tools gmessages: introduce g_log_writer_default_set_debug_domains() 2023-11-21 20:49:37 +01:00
.clang-format CI: Code check formating in CI 2019-11-21 14:03:01 -06:00
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 2012-07-30 04:09:08 -04:00
.editorconfig docs: Add .editorconfig file 2021-10-28 14:47:53 +01:00
.gitignore docs: Move INSTALL.in to INSTALL.md 2022-05-11 13:02:49 +01:00
.gitlab-ci.yml ci: Temporarily only run the FreeBSD 13 CI on a schedule 2023-12-12 16:58:27 +00:00
.gitmodules ci: Update git paths to reflect new GitLab URI 2022-11-02 16:49:51 +00:00
.lcovrc build: Move lcovrc file to root so it’s picked up by Meson 2022-04-28 11:57:45 +01:00
CODE_OF_CONDUCT.md docs: Add a code of conduct document 2022-05-11 12:30:58 +01:00
CONTRIBUTING.md ci: Use meson compile rather than bare ninja 2023-08-16 13:07:05 +01:00
COPYING docs: Add all used licenses in a REUSE-compatible directory 2022-05-17 17:23:34 +01:00
glib.doap Rename GTK+ to GTK (mostly comments and documentation) 2023-05-10 10:56:44 +07:00
INSTALL.md docs: Document issue and merge request triaging and review guidelines 2023-06-29 16:50:00 +01:00
meson_options.txt build: Rename -Dgtk_doc option to -Ddocumentation 2023-11-29 10:26:37 +00:00
meson.build build: Make packaging module required 2023-12-11 01:06:15 +03:00
NEWS 2.78.0 2023-09-08 14:42:18 +01:00
README.md Expand security policy to cover previous stable branch 2023-10-03 09:12:37 +01:00
SECURITY.md Expand security policy to cover previous stable branch 2023-10-03 09:12:37 +01:00

README.md

GLib

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.

The official download locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows.

Supported versions

Upstream GLib only supports the most recent stable release series, the previous stable release series, and the current development release series. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.

See SECURITY.md for more details.

Documentation

API documentation is available online for GLib for the:

Discussion

If you have a question about how to use GLib, seek help on GNOME’s Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib.

Reporting bugs

Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.

Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.

In bug reports please include:

  • Information about your system. For instance:
    • What operating system and version
    • For Linux, what version of the C library
    • And anything else you think is relevant.
  • How to reproduce the bug.
    • If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
  • If the bug was a crash, the exact text that was printed out when the crash occurred.
  • Further information such as stack traces may be useful, but is not necessary.

Contributing to GLib

Please follow the contribution guide to know how to start contributing to GLib.

Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):

Closes: #123

Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.