I’ve had an answer from XMOS. The [[independent_guard]] attribute actually has no effect on the execution of the code, but allows the compiler to spot a potential situation where you have added a guarded statement when you don’t intend to. There is a recommendation that it is removed in future relea...

I too would like to understand what [[independent_guard]] does. Could anyone from XMOS provide some documentation on the keyword and its intended use case?

I would like to ask the same question. I would like to leverage the infrastructure that allows any core to print to the debug console at the expense of one channel per tile, and rather than send all the messages out via xScope/xConnect to the xTimeComposer console, send them to a task of my choosing...

I would like to be able to pass a struct by reference from XC, through some C function calls, back to an XC function, where it would be usable as if it had never been passed via C. The particular struct I would like to pass is shown here. #include <xccompat.h> #ifndef __XC__ #define movable #endif t...

In this pattern there is one messaging master task and multiple worker tasks. The messaging master exists only to act as a "post office", with the rest of the work being perfomed in the worker tasks. This allows worker tasks to communicate ad-hoc with each other without requiring separate ...

Packed structures would be helpful for me too, for the same reason: being able to represent data coming from outside the system.

I should mention that I'm at xTIMEcomposer version 14.2.4.

I've encountered some interesting behaviour with uninitialised variables when they are only used within select, and when optimisation is enabled in the compiler. #include <syscall.h> #include <platform.h> #include <xs1.h> #include <xclib.h> #include <print.h> #include "debug_print.h" // Ch...

Hi all, I'm trying to design a Bidirectional Spontaneous Event Design Pattern where the main application would create an array of channels, pass all of them to one task that would be the Message Master, and the other end of each channel to a respective Task. The tasks would each identify themselves ...

Thanks Redeye, that is indeed all that is required. I had tried that already, but was being misled due to needing to also power the xtag device off and back on before the change takes effect.