zhangyu-duck commented on code in PR #21088: URL: https://github.com/apache/nuttx/pull/21088#discussion_r4419782097
########## libs/libc/machine/tricore/Kconfig: ########## @@ -2,3 +2,145 @@ # For a description of the syntax of this configuration file, # see the file kconfig-language.txt in the NuttX tools repository. # + +config TRICORE_STRING_FUNCTION + bool "Enable optimized TriCore specific string/memory functions" + default n + select TRICORE_MEMCPY + select TRICORE_MEMSET + select TRICORE_MEMMOVE + select TRICORE_MEMCMP + select TRICORE_MEMCHR + select TRICORE_STRCMP + select TRICORE_STRCPY + select TRICORE_STRLEN + select TRICORE_STRCHR + select TRICORE_STRCHRNUL + select TRICORE_STRNCMP + select TRICORE_STRNLEN + select TRICORE_STRNCPY + select TRICORE_STPCPY + select TRICORE_STRRCHR + ---help--- + Enable the full set of TriCore assembly library functions as a + group: memcpy/memset/memmove/memcmp/memchr and the string ops + strcmp/strcpy/strlen/strchr/strchrnul/strncmp/strnlen/strncpy/ + stpcpy/strrchr. Real on-board benchmarks (rzcu/lzcu B2, TC4Z9) + show the group ahead of the BSD C versions overall, most functions + substantially so. + The block-move routines (memcpy/memset/memmove) align to an 8-byte + boundary before issuing quad ld.dd/st.dd so that stores to DLMU + shared memory (0xB0/0x90, 64-bit ECC granularity) always write whole + ECC words; memcmp/strcmp are read-only (ld.w) and carry no ECC risk. Review Comment: This is just a description of an issue encountered during development; the PR itself is correct, and we avoid this problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
