Industries · Automotive
For AUTOSAR C++14 code
ByteAsk looks up AUTOSAR C++14 rules by number, quotes the rule with its page, and runs your clang-tidy and cppcheck on the change.
tool: autosar_ref started{"query":"C++ Core Guidelines CP.3 minimize explicit sharing of writable data","limit":3}tool: autosar_ref (completed in 6254ms)📚 autosar_ref · C++ Core Guidelines CP.3 minimize explicit sharing of wr…> If you don't share writable data, you can't have a data race.tool: cpp_check started{"path":".","timeout_sec":300,"use_compile_db":true}tool: cpp_check (completed in 29ms)🔧 cpp_check · .No findings.tool: cpp_tidy started{"path":"bench/shard_replay.cpp","build_dir":"."}tool: cpp_tidy (completed in 1085ms)🔧 cpp_tidy · bench/shard_replay.cppNo findings.
Recorded ByteAsk session on a C++ service: a guideline lookup with autosar_ref, then cpp_check and cpp_tidy on the changed code.
Standards it can cite
AUTOSAR C++14 · MISRA
autosar_ref: AUTOSAR C++14 · MISRA · ISO C++
AUTOSAR Guidelines for the Use of the C++14 Language in Critical and Safety-Related Systems (AP Release 18-10)§A18-5-1 required, implementation, automated · p.344
Rule A18-5-1 (required, implementation, automated)
Functions malloc, calloc, realloc and free shall not be used.
Rationale
C-style allocation/deallocation using malloc/calloc/realloc/free functions is not type safe
and does not invoke class’s constructors and destructors.
Note that invoking free function on a pointer allocated with new, as well as invoking
delete on a pointer allocated with malloc/realloc/calloc function, result in undefined
behavior.
Exception
This rule does not apply to dynamic memory allocation/deallocation performed in user-
defined overloads of new and delete operators or malloc and free functions custom
implementations.The tools it runs for Automotive
- clang-tidy
- cppcheck
- CMake
- gdb
- ASan
- Valgrind
Enterprise
See Enterprise Your code stays inside your walls
On-prem, air-gapped and bring-your-own-key deployments, with the controls your security team will ask for.