public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111779] New: Fail to vectorize the struct include struct
Date: Thu, 12 Oct 2023 07:31:39 +0000	[thread overview]
Message-ID: <bug-111779-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111779
           Summary: Fail to vectorize the struct include struct
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: juzhe.zhong at rivai dot ai
  Target Milestone: ---

#include <stdbool.h>
#include <assert.h>
struct C
{
    int c;
    int d;
    bool f :1;
    float e;
};

struct A
{
  unsigned int a;
  unsigned char c1, c2;
  bool b1 : 1;
  bool b2 : 1;
  bool b3 : 1;
  struct C b4;
};

void
foo (const struct A * __restrict x, int y)
{
  int s = 0, i = 0;
  for (i = 0; i < y; ++i)
    {
      const struct A a = x[i];
      s += a.b4.f ? 1 : 0;
    }
  assert (s == 0);
    //__builtin_abort ();
}

int
main ()
{
  struct A x[100];
  int i;
  __builtin_memset (x, -1, sizeof (x));
  for (i = 0; i < 100; i++)
    {
      x[i].b1 = false;
      x[i].b2 = false;
      x[i].b3 = false;
      x[i].b4.f = false;
    }
  foo (x, 100);
  return 0;
}

https://godbolt.org/z/KWb7c1n5h

Both SVE GCC and RVV GCC failed to vectorize it.
But Clang succeed on vectorization.

             reply	other threads:[~2023-10-12  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  7:31 juzhe.zhong at rivai dot ai [this message]
2023-10-12  8:45 ` [Bug tree-optimization/111779] " rguenth at gcc dot gnu.org
2023-10-12  9:17 ` rguenth at gcc dot gnu.org
2023-10-12 10:45 ` rguenth at gcc dot gnu.org
2023-10-13  6:34 ` cvs-commit at gcc dot gnu.org
2023-10-13  6:47 ` rguenth 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-111779-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).