Oopenvela-robotnuttx/atomic: use toolchain builtin atomic function
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
nuttx/libc: refine the atomic related Kconfig The atomic implementation logic can be broken down into follow scenarios: 1. Toolchain support, which is ideal. 2. Single-core interrupt disabling, the default for non-SMP environments. 3. If atomic instructions are supported, the libc_atomic_arch version can be implemented. Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com> | 2 个月前 | |
arch/tricore: support setjmp and longjmp Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com> | 2 个月前 | |
nuttx/libc: refine the atomic related Kconfig The atomic implementation logic can be broken down into follow scenarios: 1. Toolchain support, which is ideal. 2. Single-core interrupt disabling, the default for non-SMP environments. 3. If atomic instructions are supported, the libc_atomic_arch version can be implemented. Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com> | 2 个月前 | |
nuttx/atomic: use toolchain builtin atomic function The reason for using builtin atomic is that in C++, when include <atomic> in <nuttx/atomic.h> easily conflicts with third-party function libraries. We wanted to completely separate the implementation of <nuttx/atomic.h>. There are two points: 1. use builtin function directly. 2. Without the standard library implementation, need implement "atomic_fetch_xxx", leading conflicts with the standard library used by third-party programs, introducing redefinition issues and requiring name changes. Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com> | 2 个月前 | |
tricore/elf.h: support tricore coredump Signed-off-by: yangao1 <yangao1@xiaomi.com> | 2 个月前 | |
arch/tricore: fix setjmp/longjmp context switch Signed-off-by: zhangyu117 <zhangyu117@xiaomi.com> | 2 个月前 |