legacy: work around XCC issue in MDEF threads
The XCC compiler freaks out if a section name passed via __attribute__((section)) has parenthesis in it. This happens in the case of _MDEF_THREAD_DEFINE. It turns out the whole mechanism of placing kernel objects in completely unique sections is totally unnecessary. This patch is a workaround until we can clean this up. Change-Id: I12c88a1b8f5b27bec27d608614356c1b479c0a8c Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
This commit is contained in:
parent
dec83a7ac2
commit
ceebd823e7
|
@ -84,7 +84,7 @@ typedef int nano_context_type_t;
|
|||
abort, prio, groups) \
|
||||
char __noinit __stack _k_thread_obj_##name[stack_size]; \
|
||||
struct _static_thread_data _k_thread_data_##name __aligned(4) \
|
||||
__in_section(_static_thread_data, static, name) = \
|
||||
_GENERIC_SECTION(._static_thread_data.static.mdef) = \
|
||||
_THREAD_INITIALIZER(_k_thread_obj_##name, stack_size, \
|
||||
entry, p1, p2, p3, prio, 0, K_FOREVER, \
|
||||
abort, groups)
|
||||
|
|
Loading…
Reference in a new issue