https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70668
--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> --- On May 26, 2016 6:01:39 PM GMT+02:00, "jasonwucj at gcc dot gnu.org" <gcc-bugzi...@gcc.gnu.org> wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70668 > >Chung-Ju Wu <jasonwucj at gcc dot gnu.org> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|NEW |ASSIGNED > CC| |jakub at gcc dot gnu.org, > | |jasonwucj at gcc dot gnu.org, > | |law at redhat dot com, > | |rguenth at gcc dot gnu.org >Assignee|unassigned at gcc dot gnu.org |jasonwucj at gcc dot >gnu.org > Target Milestone|--- |7.0 > >--- Comment #8 from Chung-Ju Wu <jasonwucj at gcc dot gnu.org> --- >(In reply to Segher Boessenkool from comment #7) >> Fixed on trunk, backports pending. > >https://gcc.gnu.org/ml/gcc-patches/2016-04/msg01862.html > >Thank you for the patch to fix this issue. >Sorry I was busy on other stuff and didn't notice your mail last month. >I appreciate Jeff to help approve the patch. :) > >I think this patch is also OK for gcc-5 and gcc-6 branches. > >By the way, I guess this issue also appears on gcc-4.9 branch. >But I am not sure whether 4.9 branch is closed or not. >Maybe we need some comments from release managers. > >Jakub/Richard, would you give us some comments? :) It's still open. The gcc.Gnu.org main page states the status of active branches.
