public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98238] gcc.dg/vect/vect-cost-model-1.c etc. FAIL
Date: Mon, 11 Mar 2024 14:47:01 +0000	[thread overview]
Message-ID: <bug-98238-4-2MvMBslgQi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98238-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98238

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>:

https://gcc.gnu.org/g:4e1fcf44bdc582e71408175d75e025f5be8b0e55

commit r14-9428-g4e1fcf44bdc582e71408175d75e025f5be8b0e55
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Mon Mar 11 15:46:30 2024 +0100

    testsuite: vect: Require vect_hw_misalign in
gcc.dg/vect/vect-cost-model-1.c etc. [PR98238]

    Several gcc.dg/vect/vect-cost-model-?.c tests FAIL on 32 and 64-bit
    Solaris/SPARC:

    FAIL: gcc.dg/vect/vect-cost-model-1.c -flto -ffat-lto-objects
    scan-tree-dump vect "LOOP VECTORIZED"
    FAIL: gcc.dg/vect/vect-cost-model-1.c scan-tree-dump vect "LOOP VECTORIZED"
    FAIL: gcc.dg/vect/vect-cost-model-3.c -flto -ffat-lto-objects
    scan-tree-dump vect "LOOP VECTORIZED"
    FAIL: gcc.dg/vect/vect-cost-model-3.c scan-tree-dump vect "LOOP VECTORIZED"
    FAIL: gcc.dg/vect/vect-cost-model-5.c -flto -ffat-lto-objects
    scan-tree-dump vect "LOOP VECTORIZED"
    FAIL: gcc.dg/vect/vect-cost-model-5.c scan-tree-dump vect "LOOP VECTORIZED"

    The dumps show

   
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-cost-model-1.c:7:30:
    note: ==> examining statement: _3 = *_2;
   
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-cost-model-1.c:7:30:
    missed: unsupported unaligned access
   
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-cost-model-1.c:8:6:
    missed: not vectorized: relevant stmt not supported: _3 = *_2;

    so I think the tests need to require vect_hw_misalign.  This is what
    this patch does.

    Tested on sparc-sun-solaris2.11 and i386-pc-solaris2.11.

    2024-02-22  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

            gcc/testsuite:
            PR tree-optimization/98238
            * gcc.dg/vect/vect-cost-model-1.c (scan-tree-dump): Also require
            vect_hw_misalign.
            * gcc.dg/vect/vect-cost-model-3.c: Likewise.
            * gcc.dg/vect/vect-cost-model-5.c: Likewise.

  parent reply	other threads:[~2024-03-11 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 12:02 [Bug tree-optimization/98238] New: " ro at gcc dot gnu.org
2020-12-11 12:04 ` [Bug tree-optimization/98238] " ro at gcc dot gnu.org
2020-12-11 12:04 ` ro at gcc dot gnu.org
2021-04-27 11:39 ` jakub at gcc dot gnu.org
2021-07-28  7:05 ` rguenth at gcc dot gnu.org
2022-04-21  7:48 ` rguenth at gcc dot gnu.org
2023-05-29 10:03 ` jakub at gcc dot gnu.org
2024-02-23  9:34 ` ro at gcc dot gnu.org
2024-03-11 14:47 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-11 14:49 ` ro at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98238-4-2MvMBslgQi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).