This is the mail archive of the
mailing list for the GCC project.
Re: Option handling (support) of -fsanitize=use-after-scope
- From: Yury Gribov <y dot gribov at samsung dot com>
- To: Martin LiÅka <mliska at suse dot cz>, cfe-dev at lists dot llvm dot org, gcc at gcc dot gnu dot org
- Cc: Jakub Jelinek <jakub at redhat dot com>, Kostya Serebryany <kcc at google dot com>, Eugene Stepanov <eugeni dot stepanov at gmail dot com>, Alexey Samsonov <samsonov at google dot com>, Dmitry Vyukov <dvyukov at google dot com>
- Date: Wed, 11 May 2016 16:19:34 +0300
- Subject: Re: Option handling (support) of -fsanitize=use-after-scope
- Authentication-results: sourceware.org; auth=none
- References: <5733311B dot 90700 at suse dot cz>
On 05/11/2016 04:18 PM, Martin LiÅka wrote:
I've been working on use-after-scope sanitizer enablement in the GCC compiler () and
as I've read following submit request (), the LLVM compiler started to utilize following option:
My initial attempt was to introduce a new option value for -fsanitize option (which would make both LLVM and GCC
option compatible). Following the current behavior of the LLVM, I would have to add a new --param which would
lead to a divergence. Is the suggested approach alterable for LLVM community?
I would also suggest following default behavior:
- If -fsanitize=address or -fsanitize=kernel-address is enabled, the use-after-scope sanitization should be enabled
- Similarly, providing -fuse-after-scope should enable address sanitization (either use-space or kernel-space)
Thank you for feedback,
Cc-ed Google folks.