https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59965
--- Comment #2 from rguenther at suse dot de <rguenther at suse dot de> --- On Fri, 16 Jun 2017, marxin at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59965 > > Martin Liška <marxin at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > Last reconfirmed| |2017-06-16 > CC| |marxin at gcc dot gnu.org, > | |rguenth at gcc dot gnu.org > Ever confirmed|0 |1 > > --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- > I've noticed that discussion of the patch is stuck. Any update about it? Not really. I'm not fond of those "hacks" to make various build-configs work. If we want to sanitize the libiberty copy in cc1 then we need to compile a separate sanitized libiberty for cc1.
