!fixup address comments, thanks

Author: fhahn

clang/docs/UsersManual.rst

@@ -2489,6 +2489,8 @@ are listed below.
 
     $ clang -fuse-ld=lld -Oz -Wl,--icf=safe -fcodegen-data-use code.cc
 
+.. _strict_aliasing:
+
 Strict Aliasing
 ---------------
 
@@ -2513,8 +2515,7 @@ violates the strict aliasing rules. For example:
 
 Strict aliasing can be explicitly enabled with ``-fstrict-aliasing`` and
 disabled with ``-fno-strict-aliasing``. ``clang-cl`` defaults to
-``-fno-strict-aliasing``; see :ref:`Strict aliasing in clang-cl.
-<clang_cl_strict_aliasing>`. Otherwise, Clang defaults to ``-fstrict-aliasing``.
+``-fno-strict-aliasing``; see . Otherwise, Clang defaults to ``-fstrict-aliasing``.
 
 C and C++ specify slightly different rules for strict aliasing. To improve
 language interoperability, Clang allows two types to alias if either language
@@ -2529,7 +2530,7 @@ standard aliasing rules in the following ways:
 
 Code which violates strict aliasing has undefined behavior. A program that
 works in one version of Clang may not work in another because of changes to the
-optimizer. Clang provides a `:ref:TypeSanitizer <TypeSanitizer>` to help detect
+optimizer. Clang provides a :doc:`TypeSanitizer` to help detect
 violations of the strict aliasing rules, but it is currently still experimental.
 Code that is known to violate strict aliasing should generally be built with
 ``-fno-strict-aliasing`` if the violation cannot be fixed.
@@ -2561,7 +2562,7 @@ In Clang 20, Clang strengthened its implementation of strict aliasing for
 accesses of pointer type. Previously, all accesses of pointer type were
 permitted to alias each other, but Clang now distinguishes different pointers
 by their pointee type, except as limited by the relaxations around qualifiers
-and `void*` described above. The previous behavior of treating all pointers as
+and ``void*`` described above. The previous behavior of treating all pointers as
 aliasing can be restored using ``-fno-pointer-tbaa``.
 
 Profile Guided Optimization
@@ -5347,14 +5348,6 @@ The Visual C++ Toolset has a slightly more elaborate mechanism for detection.
 Restrictions and Limitations compared to Clang
 ----------------------------------------------
 
-.. _clang_cl_strict_aliasing:
-
-Strict Aliasing
-^^^^^^^^^^^^^^^
-
-Strict aliasing (TBAA) is always off by default in clang-cl. Whereas in clang,
-strict aliasing is turned on by default for all optimization levels.
-
-To enable LLVM optimizations based on strict aliasing rules (e.g., optimizations
-based on type of expressions in C/C++), user will need to explicitly pass
-`-fstrict-aliasing` to clang-cl.
+Strict aliasing (TBAA) is always off by default in clang-cl whereas in clang,
+strict aliasing is turned on by default for all optimization levels. For more
+details, see :ref:`Strict aliasing <strict_aliasing>`.