https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67204
Dmitry Vyukov <dvyukov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dvyukov at google dot com
--- Comment #8 from Dmitry Vyukov <dvyukov at google dot com> ---
(In reply to Manuel López-Ibáñez from comment #7)
> I'm not saying that anyone should stop working on what they are doing to
> implement this, but if a volunteer appears (Smagnet?) and wants to work on
> this, why not allow them? Perhaps they can create better documentation than
> the official one.
Hi,
It can make sense to create _some_ sanitizer-related docs in gcc. For example
clang has one:
http://clang.llvm.org/docs/AddressSanitizer.html
Such page can give a "quick start" guide and also thoroughly document
gcc-specifics (e.g. attributes, macros, features, etc). But I don't think it is
a good idea to duplicate everything. Some people will look at the "official"
documentation and be confused, gcc-hosted docs will get outdated in some ways
as well.
And we are interested in improving the "official" docs. Maybe we need to think
about a clear way to document gcc- and clang-specific aspects, and actually do
that throughout the docs.
Sanitizers will move to github soon:
https://github.com/google/sanitizers
Then it will be easier to accept pull requests for docs changes.
