On 05/13/2016 01:03 PM, Jakub Jelinek wrote:
> On Fri, May 13, 2016 at 12:26:57PM +0200, Martin Liška wrote:
>> On 05/12/2016 02:44 PM, Jakub Jelinek wrote:
>>> I think it isn't obvious that one needs to put halt_on_error=0 or
>>> halt_on_error=1 into those options and what to do if you need multiple
>>> options in there.
>>
>> What about changing the last sentence to:
>>
>> This can be overridden through a corresponding environment variable.
>
> I think it is better to be explicit, so something like:
> This can be overridden through setting the halt_on_error flag in
> the corresponding environment variable.
>
> Jakub
>
Good, I've just installed following patch as r236202.
Martin
>From f5ed058b7bacb1f75407765d2511fe1507901214 Mon Sep 17 00:00:00 2001
From: marxin <mli...@suse.cz>
Date: Fri, 13 May 2016 12:27:07 +0200
Subject: [PATCH] Enhance explanation of halt_on_error.
gcc/ChangeLog:
2016-05-13 Martin Liska <mli...@suse.cz>
* doc/invoke.texi: Enhance explanation of error recovery
of sanitizers.
---
gcc/doc/invoke.texi | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index c126644..97e5060 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -10002,9 +10002,8 @@ Even if a recovery mode is turned on the compiler side, it needs to be also
enabled on the runtime library side, otherwise the failures are still fatal.
The runtime library defaults to @code{halt_on_error=0} for
ThreadSanitizer and UndefinedBehaviorSanitizer, while default value for
-AddressSanitizer is @code{halt_on_error=1}. This can overridden through
-the following environment variables: @env{ASAN_OPTIONS}, @env{TSAN_OPTIONS},
-@env{UBSAN_OPTIONS}.
+AddressSanitizer is @code{halt_on_error=1}. This can be overridden through
+setting the @code{halt_on_error} flag in the corresponding environment variable.
Syntax without explicit @var{opts} parameter is deprecated. It is equivalent to
@smallexample
--
2.8.2
