https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80982
--- Comment #3 from wschmidt at linux dot vnet.ibm.com --- Hi Carl, Just FYI, now that you've fixed the bug, and there are no plans to backport the patch, you should go ahead and set the status of the bug to RESOLVED FIXED. I know this differs from community to community, so wanted to let you know how we do it. Thanks for the quick attention to the bug report! Bill > On Jun 7, 2017, at 5:04 PM, carll at gcc dot gnu.org > <gcc-bugzi...@gcc.gnu.org> wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80982 > > --- Comment #2 from Carl Love <carll at gcc dot gnu.org> --- > Author: carll > Date: Wed Jun 7 22:03:48 2017 > New Revision: 248997 > > URL: https://gcc.gnu.org/viewcvs?rev=248997&root=gcc&view=rev > Log: > gcc/ChangeLog: > > 2017-06-07 Carl Love <c...@us.ibm.com> > > PR target/80982 > * config/rs6000/altivec.md (double<mode>2): Fix the implementation of > for BE. > > Modified: > trunk/gcc/ChangeLog > trunk/gcc/config/rs6000/altivec.md > > -- > You are receiving this mail because: > You are on the CC list for the bug.
