summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorSebastian Dröge <sebastian@centricular.com>2023-04-07 12:15:43 +0300
committerGStreamer Marge Bot <gitlab-merge-bot@gstreamer-foundation.org>2023-04-07 11:44:45 +0000
commit94eab59667820f46222ee21dc21ada988fa2beab (patch)
treee050153975b2fddb94a5ebb4f55ceb0dd0f8eaf3 /tools
parent56f5af937854dd82cb14ae2bf166fa9ab436f30a (diff)
downloadorc-94eab59667820f46222ee21dc21ada988fa2beab.tar.gz
Don't use volatile to mean atomic
volatile is not sufficient to provide atomic guarantees and real atomics should be used instead. GCC 11 has started warning about using volatile with atomic operations. In case of orc, the volatile integers were always protected with a mutex, which makes it completely unnecessary. Part-of: <https://gitlab.freedesktop.org/gstreamer/orc/-/merge_requests/91>
Diffstat (limited to 'tools')
-rw-r--r--tools/orcc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/orcc.c b/tools/orcc.c
index 3585e93..36b0adc 100644
--- a/tools/orcc.c
+++ b/tools/orcc.c
@@ -862,7 +862,7 @@ output_code_execute (OrcProgram *p, FILE *output, int is_inline)
fprintf(output, " OrcProgram *p = _orc_program_%s;\n", p->name);
}
} else {
- fprintf(output, " static volatile int p_inited = 0;\n");
+ fprintf(output, " static int p_inited = 0;\n");
if (use_code) {
fprintf(output, " static OrcCode *c = 0;\n");
} else {