[Bug sanitizer/61978] implement blacklist for sanitizer

[marxin at gcc dot gnu.org]

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org

--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #10)
> (In reply to Stewart Martin-Haugh from comment #9)
> > Hi,
> > I see this marked as WONTFIX - still, the use-cases that Kostya identifies
> > are valid, I think. Would anyone be able to implement a patch, or suggest
> > roughly how this might work?
> 
> Although existing GCC devs may not find this feature interesting enough to
> implement it themselves, a nice, small patch properly submitted together
> with a convincingly argued rationale may get accepted. It seems this feature
> is being used not only by Chromium but also by LibreOffice, and many GCC
> users would still like to keep using GCC for building those programs.
> 
> Many features that were initially rejected have been later accepted (e.g.,
> color diagnostics). It just needs someone to get behind the idea and push
> for it in the right way.

I welcome the idea of blacklist support and I can probably come up with a patch
for that. I'm also thinking about supression of a repeated error. Running
instrumented firefox binary produces >60K errors just during start up.