https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63173
--- Comment #7 from Fei Yang <fei.yang0953 at gmail dot com> --- (In reply to clyon from comment #6) > (In reply to Ramana Radhakrishnan from comment #5) > (In reply to > Venkataramanan from comment #4) > > (In reply to Fei Yang from comment #3) > > > > (In reply to ktkachov from comment #1) > > > > Confirmed. > > > > > > > Feel free to propose a patch for them on gcc-patches along the > > > > lines > you described in: > > > https://gcc.gnu.org/ml/gcc/2014-09/msg00046.html > > > > > > > Hi, > > > To let you know, we are currently working on this > issue. > > > We are implementing these with builtins. > > > Hopefully, > the patch will be posted this week. Thank you. > > > > > > Hi Fei Yang, > > > > > Ok no issues. I will let you do this. But please asign (In reply to > Fei Yang > > from comment #3) > > > (In reply to ktkachov from comment #1) > > > > > Confirmed. > > > > > > Feel free to propose a patch for them on > gcc-patches along the > > > > lines you described in: > > > > https://gcc.gnu.org/ml/gcc/2014-09/msg00046.html > > > > > > Hi, > > > To > let you know, we are currently working on this issue. > > > We are > implementing these with builtins. > > > Hopefully, the patch will be > posted this week. Thank you. > > > > Ok. Next time please assign the > Bugzilla item to your name, so that we wont > > be duplicating the work. > > > > Linaro / Charles Bayliss was already working on this - he had patches > out in > September for this. It seems that Charles' patches cover > vldX_lane, but not vldX_dup. Hi Ramana, Do you mean this link: https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00678.html
