diff options
Diffstat (limited to 'clang/docs/UsersManual.rst')
| -rw-r--r-- | clang/docs/UsersManual.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/clang/docs/UsersManual.rst b/clang/docs/UsersManual.rst index b6ad37ea15ac..65718d204448 100644 --- a/clang/docs/UsersManual.rst +++ b/clang/docs/UsersManual.rst @@ -22,7 +22,7 @@ This document describes important notes about using Clang as a compiler for an end-user, documenting the supported features, command line options, etc. If you are interested in using Clang to build a tool that processes code, please see :doc:`InternalsManual`. If you are interested in the -`Clang Static Analyzer <http://clang-analyzer.llvm.org>`_, please see its web +`Clang Static Analyzer <https://clang-analyzer.llvm.org>`_, please see its web page. Clang is one component in a complete toolchain for C family languages. @@ -587,7 +587,7 @@ Options to Control Clang Crash Diagnostics As unbelievable as it may sound, Clang does crash from time to time. Generally, this only occurs to those living on the `bleeding -edge <http://llvm.org/releases/download.html#svn>`_. Clang goes to great +edge <https://llvm.org/releases/download.html#svn>`_. Clang goes to great lengths to assist you in filing a bug report. Specifically, Clang generates preprocessed source file(s) and associated run script(s) upon a crash. These files should be attached to a bug report to ease @@ -982,11 +982,11 @@ Controlling Static Analyzer Diagnostics ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ While not strictly part of the compiler, the diagnostics from Clang's -`static analyzer <http://clang-analyzer.llvm.org>`_ can also be +`static analyzer <https://clang-analyzer.llvm.org>`_ can also be influenced by the user via changes to the source code. See the available -`annotations <http://clang-analyzer.llvm.org/annotations.html>`_ and the +`annotations <https://clang-analyzer.llvm.org/annotations.html>`_ and the analyzer's `FAQ -page <http://clang-analyzer.llvm.org/faq.html#exclude_code>`_ for more +page <https://clang-analyzer.llvm.org/faq.html#exclude_code>`_ for more information. .. _usersmanual-precompiled-headers: @@ -2158,7 +2158,7 @@ comment(lib)`` are well supported. clang has a ``-fms-compatibility`` flag that makes clang accept enough invalid C++ to be able to parse most Microsoft headers. For example, it allows `unqualified lookup of dependent base class members -<http://clang.llvm.org/compatibility.html#dep_lookup_bases>`_, which is +<https://clang.llvm.org/compatibility.html#dep_lookup_bases>`_, which is a common compatibility issue with clang. This flag is enabled by default for Windows targets. |