- May 30, 2023
-
-
Part-of: <gstreamer/orc!102>
-
- May 29, 2023
-
-
Tim-Philipp Müller authored
Part-of: <gstreamer/orc!104>
-
Tim-Philipp Müller authored
These weren't actually exported, so could not possibly have been used. Part-of: <gstreamer/orc!104>
-
Tim-Philipp Müller authored
Those aren't public API and shouldn't be in a public header. Fixes gtkdoc-scan failure too. Part-of: <gstreamer/orc!104>
-
Sebastian Dröge authored
The flags passed in here are the orc test flags and not the target flags. Part-of: <gstreamer/orc!103>
-
Tim-Philipp Müller authored
Part-of: <gstreamer/orc!101>
-
Make it consistent with that of Linux, and remove unnecessary critical section init code Part-of: <gstreamer/orc!99>
-
Protect the entire codemem alloc/free routine with global mutex Part-of: <gstreamer/orc!99>
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- May 18, 2023
-
-
Sebastian Dröge authored
By simply reading the initialized flag with a normal read operation, the compiler is allowed to optimize code in a way that assumes this value to never ever change from another thread. As such, the second read after the mutex is taken is allowed to be optimized away and on concurrent initialization the code would be compiled by Orc twice. Similarly, if the initialized flag was set it would not be guaranteed that this thread would also see the (non-atomic) write to the code pointer yet because both threads were accessing the same variable with an atomic operation. By always accessing the initialized flag with atomic operations, both problems should be avoided now at minimal cost, especially if a C11 compatible compiler is used. Part-of: <gstreamer/orc!98>
-
- May 06, 2023
-
-
Tim-Philipp Müller authored
Part-of: <gstreamer/orc!97>
-
- Apr 24, 2023
-
-
See alias tables in ARMv8-A Architecture Reference Manual. CID 1522409 Part-of: <gstreamer/orc!95>
-
Tim-Philipp Müller authored
- can run tests on native arm64 machine - rename other arm64 jobs to cross-arm64 for clarity - fix artifacts for debian jobs - use slim images for debian jobs - add debian bullseye/bookworm variants Part-of: <gstreamer/orc!96>
-
- Apr 13, 2023
-
-
Sebastian Dröge authored
Part-of: <gstreamer/orc!30>
-
- Apr 12, 2023
-
-
Sebastian Dröge authored
Part-of: <gstreamer/orc!30>
-
Sebastian Dröge authored
Part-of: <gstreamer/orc!30>
-
Sebastian Dröge authored
Part-of: <gstreamer/orc!30>
-
Sebastian Dröge authored
And change it to the same format as used by orcc now. Part-of: <gstreamer/orc!30>
-
Sebastian Dröge authored
Part-of: <gstreamer/orc!30>
-
Sebastian Dröge authored
Part-of: <gstreamer/orc!30>
-
useful while writing orc programs to have faster feedback. Part-of: <gstreamer/orc!30>
-
In general, error/warnings should be sent to stderr to not pollute the output, so do that also for generated output. Part-of: <gstreamer/orc!30>
-
Send both usage instructions and errors to stderr, since the actual output may be sent to stdout. Avoids output pollution. Part-of: <gstreamer/orc!30>
-
orc_parse_code has much better error report than orc_parse_full, so orcc should make use of it. Part-of: <gstreamer/orc!30>
-
It is now empty and unneeded legacy Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <!30>
-
Part-of: <gstreamer/orc!30>
-
Part-of: <gstreamer/orc!30>
-
Co-authored-by: Sebastian Dröge <sebastian@centricular.com> Part-of: <gstreamer/orc!30>
-