On Fri, Jan 27, 2017 at 10:02:41AM -0600, Bill Schmidt wrote:
> > For the record: approved for trunk. Thanks!
> >
> Would it be all right to back port this to GCC 5 and 6 after some burn-in?
> I see now that the bug was reported against GCC 5.
Sure. It only fixes a testcase so it won't really
> On Jan 26, 2017, at 6:40 PM, Segher Boessenkool
> wrote:
>
> On Thu, Jan 26, 2017 at 05:31:16PM -0600, Bill Schmidt wrote:
>>> So for older targets it used to run the final, but not after the patch; and
>>> for newer targets it used to not run it, but it does
On Thu, Jan 26, 2017 at 05:31:16PM -0600, Bill Schmidt wrote:
> > So for older targets it used to run the final, but not after the patch; and
> > for newer targets it used to not run it, but it does after the patch? So
> > it is meant to be two changes?
>
> Correct, I forgot to point out that
> On Jan 26, 2017, at 5:15 PM, Segher Boessenkool
> wrote:
>
> On Thu, Jan 26, 2017 at 04:36:31PM -0600, Bill Schmidt wrote:
-/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" {
target { ! vect_no_align } } } } */
-/* { dg-final {
On Thu, Jan 26, 2017 at 04:36:31PM -0600, Bill Schmidt wrote:
> >> -/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" {
> >> target { ! vect_no_align } } } } */
> >> -/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 1
> >> "vect" { target { ! vect_no_align } }
On Thu, Jan 26, 2017 at 03:14:47PM -0600, Bill Schmidt wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65484 identifies an
> issue whether g++.dg/vect/pr36648.cc fails on older POWER hardware.
> This is due to a decision made in November 2010 to include the
> flag -mno-allow-movmisalign in
> On Jan 26, 2017, at 4:29 PM, Segher Boessenkool
> wrote:
>
> On Thu, Jan 26, 2017 at 03:14:47PM -0600, Bill Schmidt wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65484 identifies an
>> issue whether g++.dg/vect/pr36648.cc fails on older POWER hardware.
>>
Hi,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65484 identifies an
issue whether g++.dg/vect/pr36648.cc fails on older POWER hardware.
This is due to a decision made in November 2010 to include the
flag -mno-allow-movmisalign in check_vect_support_and_set_flags,
which governs the vectorizer