Merge commit '58ce53278548' from apple/master into swift/master-next

Author: git apple-llvm automerger

clang/www/OpenProjects.html

@@ -44,19 +44,19 @@ <h1>Open Clang Projects</h1>
 Clang is built as a set of libraries, which means that it is possible to
 implement capabilities similar to other source language tools, improving them
 in various ways.  Three examples are <a
-href="http://distcc.samba.org/">distcc</a>, the <a
+href="https://github.com/distcc">distcc</a>, the <a
 href="http://delta.tigris.org/">delta testcase reduction tool</a>, and the
 "indent" source reformatting tool.
 distcc can be improved to scale better and be more efficient.  Delta could be
 faster and more efficient at reducing C-family programs if built on the clang
 preprocessor. The clang-based indent replacement,
-<a href="http://clang.llvm.org/docs/ClangFormat.html">clang-format</a>,
+<a href="https://clang.llvm.org/docs/ClangFormat.html">clang-format</a>,
 could be taught to handle simple structural rules like those in <a
-href="http://llvm.org/docs/CodingStandards.html#hl_earlyexit">the LLVM coding
+href="https://llvm.org/docs/CodingStandards.html#use-early-exits-and-continue-to-simplify-code">the LLVM coding
 standards</a>.</li>
 
-<li><b>Use clang libraries to extend Ragel with a JIT</b>: <a 
-href="http://research.cs.queensu.ca/~thurston/ragel/">Ragel</a> is a state
+<li><b>Use clang libraries to extend Ragel with a JIT</b>: <a
+href="https://www.colm.net/open-source/ragel/">Ragel</a> is a state
 machine compiler that lets you embed C code into state machines and generate
 C code.  It would be relatively easy to turn this into a JIT compiler using
 LLVM.</li>

clang/www/UniversalDriver.html

@@ -45,7 +45,7 @@ <h1>The Clang Universal Driver Project</h1>
 development. Stay tuned for more information, and of course, patches
 welcome!</p>
 
-<p>See also <a href="http://llvm.org/PR4127">PR4127</a>.</p>
+<p>See also <a href="https://llvm.org/PR4127">PR4127</a>.</p>
 
 <h2>Existing Solutions and Related Work</h2>
 
@@ -55,14 +55,14 @@ <h2>Existing Solutions and Related Work</h2>
     and <tt>-m64</tt> solve a small subset of the problem for specific
     architectures.</li>
 
-  <li>gcc's <a href="http://www.airs.com/ian/configure/configure_8.html">multilibs</a>
+  <li>gcc's <a href="https://www.airs.com/ian/configure/configure_8.html">multilibs</a>
     solve the part of the problem that relates to finding appropriate libraries
     and include files based on particular feature support (soft float,
     etc.).</li>
 
   <li>Apple's "driver driver" supported by gcc and clang solve a subset of the
     problem by supporting <tt>-arch</tt>. Apple also provides a tool chain which
-    supports <a href="http://en.wikipedia.org/wiki/Universal_binary">universal
+    supports <a href="https://en.wikipedia.org/wiki/Universal_binary">universal
     binaries</a> and object files which may include data for multiple
     architectures. See <a href="http://developer.apple.com/mac/library/technotes/tn2005/tn2137.html">TN2137</a>
     for an example of how this is used.</li>
@@ -73,7 +73,7 @@ <h2>Existing Solutions and Related Work</h2>
     does not match well with tools which are inherently capable of cross
     compiling.</li>
 
-  <li>The Debian <a href="http://wiki.debian.org/ArmEabiPort">ArmEabiPort</a>
+  <li>The Debian <a href="https://wiki.debian.org/ArmEabiPort">ArmEabiPort</a>
     wiki page for their work to support the ARM EABI provide an interesting
     glimpse into how related issues impact the operating system distribution.</li>
 

clang/www/analyzer/alpha_checks.html

@@ -930,9 +930,9 @@ <h3 id="unix_alpha_checkers">Unix Alpha Checkers</h3>
 Check for misuses of stream APIs:<div class=functions>
 fopen<br>
 fclose</div>(demo checker, the subject of the demo
-(<a href="http://llvm.org/devmtg/2012-11/Zaks-Rose-Checker24Hours.pdf">Slides</a>
+(<a href="https://llvm.org/devmtg/2012-11/Zaks-Rose-Checker24Hours.pdf">Slides</a>
 ,<a href="https://youtu.be/kdxlsP5QVPw">Video</a>)
-by Anna Zaks and Jordan Rose presented at the <a href="http://llvm.org/devmtg/2012-11/">
+by Anna Zaks and Jordan Rose presented at the <a href="https://llvm.org/devmtg/2012-11/">
 2012 LLVM Developers' Meeting).</a></div></div></a></td>
 <td><div class="exampleContainer expandable">
 <div class="example"><pre>

clang/www/analyzer/annotations.html

@@ -17,18 +17,18 @@
 <h1>Source Annotations</h1>
 
 <p>The Clang frontend supports several source-level annotations in the form of
-<a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html">GCC-style
+<a href="https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html">GCC-style
 attributes</a> and pragmas that can help make using the Clang Static Analyzer
 more useful. These annotations can both help suppress false positives as well as
 enhance the analyzer's ability to find bugs.</p>
 
 <p>This page gives a practical overview of such annotations. For more technical
 specifics regarding Clang-specific annotations please see the Clang's list of <a
-href="http://clang.llvm.org/docs/LanguageExtensions.html">language
+href="https://clang.llvm.org/docs/LanguageExtensions.html">language
 extensions</a>. Details of &quot;standard&quot; GCC attributes (that Clang also
-supports) can be found in the <a href="http://gcc.gnu.org/onlinedocs/gcc/">GCC
+supports) can be found in the <a href="https://gcc.gnu.org/onlinedocs/gcc/">GCC
 manual</a>, with the majority of the relevant attributes being in the section on
-<a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html">function
+<a href="https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html">function
 attributes</a>.</p>
 
 <p>Note that attributes that are labeled <b>Clang-specific</b> are not
@@ -68,7 +68,7 @@ <h4>Specific Topics</h4>
         <li><a href="#attr_os_consumes_this">Attribute 'os_consumes_this'</a></li>
         <li><a href="#os_out_parameters">Out Parameters</a></li>
       </ul>
-    
+
     </li>
   </ul>
 </li>
@@ -91,7 +91,7 @@ <h4 id="attr_nonnull">Attribute 'nonnull'</h4>
 <p>The analyzer recognizes the GCC attribute 'nonnull', which indicates that a
 function expects that a given function parameter is not a null pointer. Specific
 details of the syntax of using the 'nonnull' attribute can be found in <a
-href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#index-g_t_0040code_007bnonnull_007d-function-attribute-2263">GCC's
+href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-nonnull-function-attribute">GCC's
 documentation</a>.</p>
 
 <p>Both the Clang compiler and GCC will flag warnings for simple cases where a
@@ -108,7 +108,7 @@ <h4 id="attr_nonnull">Attribute 'nonnull'</h4>
 int bar(int*p, int q, int *r) __attribute__((nonnull(1,3)));
 
 int foo(int *p, int *q) {
-   return !p ? bar(q, 2, p) 
+   return !p ? bar(q, 2, p)
              : bar(p, 2, q);
 }
 </pre>
@@ -138,8 +138,8 @@ <h3 id="cocoa_mem">Cocoa &amp; Core Foundation Memory Management
 <p>One can educate the analyzer (and others who read your code) about methods or
 functions that deviate from the Cocoa and Core Foundation conventions using the
 attributes described here. However, you should consider using proper naming
-conventions or the <a 
-href="http://clang.llvm.org/docs/LanguageExtensions.html#the-objc-method-family-attribute"><tt>objc_method_family</tt></a>
+conventions or the <a
+href="https://clang.llvm.org/docs/LanguageExtensions.html#the-objc-method-family-attribute"><tt>objc_method_family</tt></a>
 attribute, if applicable.</p>
 
 <h4 id="attr_ns_returns_retained">Attribute 'ns_returns_retained'
@@ -236,7 +236,7 @@ <h4 id="attr_cf_returns_retained">Attribute 'cf_returns_retained'
 
 <p>The GCC-style (Clang-specific) attribute 'cf_returns_retained' allows one to
 annotate an Objective-C method or C function as returning a retained Core
-Foundation object that the caller is responsible for releasing. The 
+Foundation object that the caller is responsible for releasing. The
 CoreFoundation framework defines a macro <b><tt>CF_RETURNS_RETAINED</tt></b>
 that is functionally equivalent to the one shown below.</p>
 
@@ -323,7 +323,7 @@ <h4 id="attr_cf_returns_not_retained">Attribute 'cf_returns_not_retained'
 method may appear to obey the Core Foundation or Cocoa conventions and return
 a retained Core Foundation object, this attribute can be used to indicate that
 the object reference returned should not be considered as an
-&quot;owning&quot; reference being returned to the caller. The 
+&quot;owning&quot; reference being returned to the caller. The
 CoreFoundation framework defines a macro <b><tt>CF_RETURNS_NOT_RETAINED</tt></b>
 that is functionally equivalent to the one shown below.</p>
 
@@ -353,8 +353,8 @@ <h4 id="attr_ns_consumed">Attribute 'ns_consumed'
 <p>The 'ns_consumed' attribute can be placed on a specific parameter in either
 the declaration of a function or an Objective-C method. It indicates to the
 static analyzer that a <tt>release</tt> message is implicitly sent to the
-parameter upon completion of the call to the given function or method. The 
-Foundation framework defines a macro <b><tt>NS_RELEASES_ARGUMENT</tt></b> that 
+parameter upon completion of the call to the given function or method. The
+Foundation framework defines a macro <b><tt>NS_RELEASES_ARGUMENT</tt></b> that
 is functionally equivalent to the <tt>NS_CONSUMED</tt> macro shown below.</p>
 
 <p><b>Example</b></p>
@@ -408,7 +408,7 @@ <h4 id="attr_cf_consumed">Attribute 'cf_consumed'
 to the given function or method. The CoreFoundation framework defines a macro
 <b><tt>CF_RELEASES_ARGUMENT</tt></b> that is functionally equivalent to the
 <tt>CF_CONSUMED</tt> macro shown below.</p>
-    
+
 <p>Operationally this attribute is nearly identical to 'ns_consumed'.</p>
 
 <p><b>Example</b></p>
@@ -438,7 +438,7 @@ <h4 id="attr_cf_consumed">Attribute 'cf_consumed'
 void test2() {
   CFDateRef date = CFDateCreate(0, CFAbsoluteTimeGetCurrent());
   consume_CFDate(date); <b><i>// No leak, including under GC!</i></b>
-  
+
 }
 
 @interface Foo : NSObject
@@ -463,7 +463,7 @@ <h4 id="attr_ns_consumes_self">Attribute 'ns_consumes_self'
 follow the standard Cocoa naming conventions.</p>
 
 <p><b>Example</b></p>
-  
+
 <pre class="code_example">
 #ifndef __has_feature
 #define __has_feature(x) 0 // Compatibility with non-clang compilers.
@@ -573,8 +573,8 @@ <h5>Example</h5>
   OSObject *f;
   LIBKERN_RETURNS_NOT_RETAINED OSObject *myFieldGetter();
 }
- 
- 
+
+
 // Note that the annotation only has to be applied to the function declaration.
 OSObject * MyClass::myFieldGetter() {
   return f;
@@ -633,7 +633,7 @@ <h4 id="os_out_parameters">Out Parameters</h4>
 void getterViaOutParam(LIBKERN_RETURNS_NOT_RETAINED OSObject **obj)
 </pre>
 <p>
-In such cases a retained object is written into an out parameter, which the caller has then to release in order to avoid a leak. 
+In such cases a retained object is written into an out parameter, which the caller has then to release in order to avoid a leak.
 </p>
 
 <p>These two cases are simple - but in practice a functions returning an out-parameter usually also return a return code, and then an out parameter may or may not be written, which conditionally depends on the exit code, e.g.:</p>
@@ -718,7 +718,7 @@ <h2 id="custom_assertions">Custom Assertion Handlers</h2>
 <p>The analyzer knows about several well-known assertion handlers, but can
 automatically infer if a function should be treated as an assertion handler if
 it is annotated with the 'noreturn' attribute or the (Clang-specific)
-'analyzer_noreturn' attribute. Note that, currently, clang does not support 
+'analyzer_noreturn' attribute. Note that, currently, clang does not support
 these attributes on Objective-C methods and C++ methods.</p>
 
 <h4 id="attr_noreturn">Attribute 'noreturn'</h4>
@@ -729,7 +729,7 @@ <h4 id="attr_noreturn">Attribute 'noreturn'</h4>
 
 <p>Specific details of the syntax of using the 'noreturn' attribute can be found
 in <a
-href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#index-g_t_0040code_007bnoreturn_007d-function-attribute-2264">GCC's
+href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-noreturn-function-attribute">GCC's
 documentation</a>.</p>
 
 <p>Not only does the analyzer exploit this information when pruning false paths,

clang/www/analyzer/available_checks.html

@@ -29,8 +29,8 @@ <h3>Writeups with examples of some of the bugs that the analyzer finds</h3>
 <ul>
 <li><a href="http://www.mobileorchard.com/bug-finding-with-clang-5-resources-to-get-you-started/">Bug Finding With Clang: 5 Resources To Get You Started</a></li>
 <li><a href="http://fruitstandsoftware.com/blog/index.php/2008/08/finding-memory-leaks-with-the-llvmclang-static-analyzer/#comment-2">Finding Memory Leaks With The LLVM/Clang Static Analyzer</a></li>
-<li><a href="http://www.rogueamoeba.com/utm/2008/07/14/the-clang-static-analyzer/">Under the Microscope - The Clang Static Analyzer</a></li>
-<li><a href="http://www.mikeash.com/?page=pyblog/friday-qa-2009-03-06-using-the-clang-static-analyzer.html">Mike Ash - Using the Clang Static Analyzer</a></li>
+<li><a href="https://weblog.rogueamoeba.com/2008/07/14/the-clang-static-analyzer/">Under the Microscope - The Clang Static Analyzer</a></li>
+<li><a href="https://www.mikeash.com/pyblog/friday-qa-2009-03-06-using-the-clang-static-analyzer.html">Mike Ash - Using the Clang Static Analyzer</a></li>
 </ul>
 
 <h2 id="default_checkers">Default Checkers</h2>