summaryrefslogtreecommitdiff
path: root/pkcs11/secret-store
diff options
context:
space:
mode:
authorSimon McVittie <smcv@debian.org>2021-09-26 16:41:30 +0100
committerNiels De Graef <nielsdegraef@gmail.com>2022-05-21 10:38:47 +0000
commiteada1440fec9a082d199ef83bb92b5af149d4c1f (patch)
treedf9dcf50cee50dc7a302c5f7308f20f189573e2e /pkcs11/secret-store
parent232010c1041b7bd6e7f4757b87e157a05a28425d (diff)
downloadgnome-keyring-eada1440fec9a082d199ef83bb92b5af149d4c1f.tar.gz
Stop using volatile in conjunction with atomic operationswip/smcv/fix-ci
As discussed in <https://gitlab.gnome.org/GNOME/glib/-/issues/600>, the volatile qualifier rarely has the semantics that are desired in C/C++. With recent gcc versions, combining pointers to volatile-qualified types with the __atomic_foo() family of builtins causes compiler warnings. http://c.isvolatileusefulwiththreads.com/ has some other useful references. Signed-off-by: Simon McVittie <smcv@debian.org>
Diffstat (limited to 'pkcs11/secret-store')
-rw-r--r--pkcs11/secret-store/gkm-secret-fields.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/pkcs11/secret-store/gkm-secret-fields.c b/pkcs11/secret-store/gkm-secret-fields.c
index 7e4559c6..71620499 100644
--- a/pkcs11/secret-store/gkm-secret-fields.c
+++ b/pkcs11/secret-store/gkm-secret-fields.c
@@ -124,7 +124,7 @@ compat_hash_value_as_string (const gchar *value)
GType
gkm_secret_fields_boxed_type (void)
{
- static volatile gsize type_inited = 0;
+ static gsize type_inited = 0;
static GType type = 0;
if (g_once_init_enter (&type_inited)) {