public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114072] New: gcc.dg/vect/vect-pr111779.c FAILs
Date: Fri, 23 Feb 2024 09:58:17 +0000	[thread overview]
Message-ID: <bug-114072-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114072
           Summary: gcc.dg/vect/vect-pr111779.c FAILs
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: rguenth at gcc dot gnu.org
  Target Milestone: ---
            Target: sparc*-sun-solaris2.11

The gcc.dg/vect/vect-pr111779.c test FAILs on 32 and 64-bit Solaris/SPARC
since its introduction:

+FAIL: gcc.dg/vect/vect-pr111779.c -flto -ffat-lto-objects  scan-tree-dump vect
"LOOP VECTORIZED"
+FAIL: gcc.dg/vect/vect-pr111779.c scan-tree-dump vect "LOOP VECTORIZED"

The dump has

/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-pr111779.c:26:17:
note:   ==> examining statement: _4 = a$b4_6 >> 7;
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-pr111779.c:26:17:
note:   vect_is_simple_use: operand BIT_FIELD_REF <*_3.b4, 8, 64>, type of def:
internal
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-pr111779.c:26:17:
note:   vect_is_simple_use: vectype vector(8) unsigned char
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-pr111779.c:26:17:
note:   vect_is_simple_use: operand 7, type of def: constant
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-pr111779.c:26:17:
missed:   op not supported by target.
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-pr111779.c:29:23:
missed:   not vectorized: relevant stmt not supported: _4 = a$b4_6 >> 7;

but I don't know which vect_* keyword would capture this.

             reply	other threads:[~2024-02-23  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  9:58 ro at gcc dot gnu.org [this message]
2024-05-22  9:16 ` [Bug tree-optimization/114072] " ro at gcc dot gnu.org
2024-05-22  9:36 ` rguenth at gcc dot gnu.org
2024-05-22 11:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-22 12:01 ` rguenther at suse dot de
2024-05-22 12:14 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-22 12:30 ` rguenther at suse dot de
2024-05-23  7:54 ` cvs-commit at gcc dot gnu.org
2024-05-23  7:57 ` 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-114072-4@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).