================
@@ -1,20 +1,20 @@
-.. title:: clang-tidy - bugprone-default-operator-new-on-overaligned-type
+```{title} clang-tidy - bugprone-default-operator-new-on-overaligned-type
+```
-bugprone-default-operator-new-on-overaligned-type
-=================================================
+# bugprone-default-operator-new-on-overaligned-type
-Flags uses of default ``operator new`` where the type has extended
+Flags uses of default `operator new` where the type has extended
alignment (an alignment greater than the fundamental alignment).
-The default ``operator new`` is guaranteed to provide the correct alignment
+The default `operator new` is guaranteed to provide the correct alignment
if the requested alignment is less or equal to the fundamental alignment.
-Only cases are detected (by design) where the ``operator new`` is not
+Only cases are detected (by design) where the `operator new` is not
user-defined and is not a placement new (the reason is that in these cases we
assume that the user provided the correct memory allocation).
-References
-----------
+## References
This check corresponds to the CERT C++ Coding Standard rule
-`MEM57-CPP. Avoid using default operator new for over-aligned types
-<https://cmu-sei.github.io/secure-coding-standards/sei-cert-cpp-coding-standard/rules/memory-management-mem/mem57-cpp/>`_.
+[MEM57-CPP. Avoid using default operator new for over-aligned
types][mem57-cpp].
----------------
zeyi2 wrote:
Same as above.
https://github.com/llvm/llvm-project/pull/210467
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
