[cfe-dev] [clang-tidy][RFC] Add Autosar C++14 clang-tidy module?

[Danny Mösch via cfe-dev]

I like the idea of adding an AUTOSAR module to clang-tidy!

I know of at least two projects which have some work done already. The first one was started in the context of Google Summer of Code. You can find the final report at https://docs.google.com/document/d/1r6H5eYOji3mytkdpNJFPuc4PdmE2ZbrFeNAhEqkQIpU/edit <https://docs.google.com/document/d/1r6H5eYOji3mytkdpNJFPuc4PdmE2ZbrFeNAhEqkQIpU/edit>. Some rules have already been implemented in an LLVM fork at https://github.com/Bareflank/llvm-project <https://github.com/Bareflank/llvm-project> as mentioned in the report. The second one is a commercial project which has been presented at the 2020 Developers Meeting: https://www.youtube.com/watch?v=-6dL-7xkIV0 <https://www.youtube.com/watch?v=-6dL-7xkIV0>. At the time of the presentation it was not quite clear whether the source code will be open-sourced at some point.

> All in all, Autosar is not perfect but it's an important enabler for e.g. the automotive industry to finally leave MISRA C++08 and move to modern C++14. There's plans for new MISRA guidelines covering C++17 but it's unclear when they'll be published, so we need to live with Autosar for a little more.

Talking about MISRA, is there a reason why there are no ambitions to add another module for the MISRA guidelines? I would be very interested in clang-tidy being able to check for MSRA rules, too. Is it because the guidelines have to be licensed/bought? Is it not allowed to make them public in any way? Does anyone know?

Greetings,
Danny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20211106/6bac4fe8/attachment.html>