Update

Builtin-options.html

@@ -771,10 +771,25 @@ <h2 id="base-options">Base options</h2>
 </tr>
 </tbody>
 </table>
-<p>The value of <code>b_sanitize</code> can be one of: <code>none</code>, <code>address</code>, <code>thread</code>,
-<code>undefined</code>, <code>memory</code>, <code>leak</code>, <code>address,undefined</code>, but note that some
-compilers might not support all of them. For example Visual Studio
-only supports the address sanitizer.</p>
+<p>The default and possible values of sanitizers changed in 1.8. Before 1.8 they
+were string values, and restricted to a specific subset of values: <code>none</code>,
+<code>address</code>, <code>thread</code>, <code>undefined</code>, <code>memory</code>, <code>leak</code>, or <code>address,undefined</code>. In
+1.8 it was changed to a free form array of sanitizers, which are checked by a
+compiler and linker check. For backwards compatibility reasons
+<code>get_option('b_sanitize')</code> continues to return a string with the array values
+separated by a comma. Furthermore:</p>
+<ul>
+<li>
+<p>If the <code>b_sanitize</code> option is empty, the <code>'none'</code> string is returned.</p>
+</li>
+<li>
+<p>If it contains only the values <code>'address'</code> and <code>'undefined'</code>, they are
+always returned as the <code>'address,undefined'</code> string, in this order.</p>
+</li>
+<li>
+<p>Otherwise, the array elements are returned in undefined order.</p>
+</li>
+</ul>
 <p>* &lt; 0 means disable, == 0 means automatic selection, &gt; 0 sets a specific number to use</p>
 <p>LLVM supports <code>thin</code> lto, for more discussion see <a href="https://clang.llvm.org/docs/ThinLTO.html">LLVM's documentation</a></p>
 <p><a name="b_vscrt-from_buildtype"></a>

Release-notes-for-1-8-0.html

@@ -211,6 +211,21 @@
 	<div id="main">
 				    <div id="page-description" data-hotdoc-role="main">
         <h1 id="new-features-in-development">New features (in development)</h1>
+<h2 id="changes-to-the-b_sanitize-option">Changes to the b_sanitize option</h2>
+<p>Before 1.8 the <code>b_sanitize</code> option was a combo option, which is an enumerated
+set of values. In 1.8 this was changed to a free-form array of options where
+available sanitizers are not hardcoded anymore but instead verified via a
+compiler check.</p>
+<p>This solves a number of longstanding issues such as:</p>
+<ul>
+<li>Sanitizers may be supported by a compiler, but not on a specific platform
+(OpenBSD).</li>
+<li>New sanitizers are not recognized by Meson.</li>
+<li>Using sanitizers in previously-unsupported combinations.</li>
+</ul>
+<p>To not break backwards compatibility, calling <code>get_option('b_sanitize')</code>
+continues to return the configured value as a string, with a guarantee that
+<code>address,undefined</code> remains ordered.</p>
 <h2 id="version_compare-now-accept-multiple-compare-strings">
 <code>version_compare</code> now accept multiple compare strings</h2>
 <p>Is it now possible to compare version against multiple values, to check for

assets/js/search/Changes

@@ -1 +1 @@
-urls_downloaded_cb({"token":"Changes","urls":[{"url":"Adding-new-projects-to-wrapdb.html#changes-to-original-source","node_type":"h2","page":"Adding new projects to WrapDB","sections":["Adding new projects to WrapDB","Changes to original source"],"context":{"gi-language":["default"]}},{"url":"Commands.html#configure","node_type":"p","page":"Command-line commands","sections":["Command-line commands","configure"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-0-57-0.html#msvcclangcl-argument-changescleanup","node_type":"h2","page":"Release 0.57.0","sections":["New features","MSVC/Clang-Cl Argument Changes/Cleanup"],"context":{"gi-language":["default"]}}]});
+urls_downloaded_cb({"token":"Changes","urls":[{"url":"Adding-new-projects-to-wrapdb.html#changes-to-original-source","node_type":"h2","page":"Adding new projects to WrapDB","sections":["Adding new projects to WrapDB","Changes to original source"],"context":{"gi-language":["default"]}},{"url":"Commands.html#configure","node_type":"p","page":"Command-line commands","sections":["Command-line commands","configure"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-0-57-0.html#msvcclangcl-argument-changescleanup","node_type":"h2","page":"Release 0.57.0","sections":["New features","MSVC/Clang-Cl Argument Changes/Cleanup"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-8-0.html#changes-to-the-b_sanitize-option","node_type":"h2","page":"Release 1.8.0 (in development)","sections":["New features (in development)","Changes to the b_sanitize option"],"context":{"gi-language":["default"]}}]});

assets/js/search/OpenBSD

@@ -1 +1 @@
-urls_downloaded_cb({"token":"OpenBSD","urls":[{"url":"Release-notes-for-0-62-0.html#new-custom-dependency-for-libdl","node_type":"p","page":"Release 0.62.0","sections":["New features","New custom dependency for libdl"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-0-64-0.html#bsd-support-for-the-jni-dependency","node_type":"p","page":"Release 0.64.0","sections":["New features","BSD support for the jni dependency"],"context":{"gi-language":["default"]}}]});
+urls_downloaded_cb({"token":"OpenBSD","urls":[{"url":"Release-notes-for-0-62-0.html#new-custom-dependency-for-libdl","node_type":"p","page":"Release 0.62.0","sections":["New features","New custom dependency for libdl"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-0-64-0.html#bsd-support-for-the-jni-dependency","node_type":"p","page":"Release 0.64.0","sections":["New features","BSD support for the jni dependency"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-8-0.html#changes-to-the-b_sanitize-option","node_type":"ul","page":"Release 1.8.0 (in development)","sections":["New features (in development)","Changes to the b_sanitize option"],"context":{"gi-language":["default"]}}]});

assets/js/search/Sanitizers

@@ -1 +1 @@
-urls_downloaded_cb({"token":"Sanitizers","urls":[{"url":"Release-notes-for-0-42-0.html#simultaneous-use-of-address-and-undefined-behavior-sanitizers","node_type":"h2","page":"Release 0.42","sections":["New features","Simultaneous use of Address- and Undefined Behavior Sanitizers"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-3-0.html#tests-now-abort-on-errors-by-default-under-sanitizers","node_type":"p","page":"Release 1.3.0","sections":["New features","Tests now abort on errors by default under sanitizers"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-4-0.html#tests-now-abort-on-errors-by-default-under-more-sanitizers","node_type":"p","page":"Release 1.4.0","sections":["New features","Tests now abort on errors by default under more sanitizers"],"context":{"gi-language":["default"]}}]});
+urls_downloaded_cb({"token":"Sanitizers","urls":[{"url":"Release-notes-for-0-42-0.html#simultaneous-use-of-address-and-undefined-behavior-sanitizers","node_type":"h2","page":"Release 0.42","sections":["New features","Simultaneous use of Address- and Undefined Behavior Sanitizers"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-3-0.html#tests-now-abort-on-errors-by-default-under-sanitizers","node_type":"p","page":"Release 1.3.0","sections":["New features","Tests now abort on errors by default under sanitizers"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-4-0.html#tests-now-abort-on-errors-by-default-under-more-sanitizers","node_type":"p","page":"Release 1.4.0","sections":["New features","Tests now abort on errors by default under more sanitizers"],"context":{"gi-language":["default"]}},{"url":"Release-notes-for-1-8-0.html#changes-to-the-b_sanitize-option","node_type":"ul","page":"Release 1.8.0 (in development)","sections":["New features (in development)","Changes to the b_sanitize option"],"context":{"gi-language":["default"]}}]});