https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65285

Kostya Serebryany <kcc at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #10 from Kostya Serebryany <kcc at gcc dot gnu.org> ---
(In reply to Peter Wu from comment #9)
> Tested with
> clang version 3.7.0 (http://llvm.org/git/clang.git
> 6b7e300a9c14a2ff364d8ef8a0f7510378f38dbc) (http://llvm.org/git/llvm
> 258b7710d59c086656f7b26f02326d7ca69d71fd)
> 
> (http://llvm.org/git/compiler-rt.git
> 70b3c4464a4067db2cd9862736611fdf6739f451)
> 
> The output is still:
> AddressSanitizer can not describe address in more detail (wild memory access
> suspected).
> 
> I can however live with the -fno-common workaround (which sounds like a good
> idea overall). 

Exactly, we recommend using -fno-common with asan for C to find more bugs. 


> I'll leave it up to you whether it will be closed as WONTFIX.
> 
> Thanks for your hints!

Reply via email to