On Mon, Sep 26, 2016 at 11:56:01AM +0200, Martin Liška wrote:
> @item -fsanitize=kernel-address
> @opindex fsanitize=kernel-address
> @@ -10169,17 +10170,19 @@ details. The run-time behavior can be influenced
> using the @env{TSAN_OPTIONS}
> environment variable; see
> @url{https://github.com/
ouldn't it be instead
> if (sanitizer_opts[i].flag == SANITIZE_UNDEFINED)
> flags |= SANITIZE_UNDEFINED & ~(SANITIZE_UNREACHABLE | SANITIZE_RETURN);
> else
> flags |= sanitizer_opts[i].flag;
> ?
Yes, my approach was wrong ;) your looks better. I'm adding a ne
On Fri, Sep 23, 2016 at 01:53:48PM +0200, Martin Liška wrote:
> 3) -fsanitize=leak is combinable with -fsanitize=address or
>-fsanitize=thread
Is it really combinable with -fsanitize=thread? I thought only libasan
or liblsan provides the leak checker. Anyway, I can't find where in the
patch
xin
Date: Fri, 23 Sep 2016 10:16:10 +0200
Subject: [PATCH] Fix handling of -fsanitize-recover* options.
gcc/ChangeLog:
2016-09-23 Martin Liska
* common.opt: Exclude SANITIZE_UNREACHABLE and SANITIZE_RETURN
from default sanitize recover values.
* doc/invoke.texi: Fix documentation related
