public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68703] __attribute__((vector_size(N))) template member confusion
Date: Thu, 04 Jan 2024 11:46:44 +0000	[thread overview]
Message-ID: <bug-68703-4-bWIb7IXvnU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68703-4@http.gcc.gnu.org/bugzilla/>

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

Richard Sandiford <rsandifo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rsandifo at gcc dot gnu.org

--- Comment #11 from Richard Sandiford <rsandifo at gcc dot gnu.org> ---
FWIW, the following adaption of the original testcase still fails on trunk, but
is accepted by Clang:

template <int N = 4>
struct D {
    using t = int __attribute__((vector_size(N * sizeof(int))));
    t v;
    int f1() { return this->v[N-1]; }
    int f2() { return v[N-1]; }
};

int main(int ac, char**)
{
  D<> d = { { ac } };
  return d.f1() + d.f2();
}

Same with a typedef instead of "using".  But that's probably just another
instance of PR88600/PR58855.

      parent reply	other threads:[~2024-01-04 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-68703-4@http.gcc.gnu.org/bugzilla/>
2020-11-10 23:52 ` ncm at cantrip dot org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2021-05-04 19:27 ` ncm at cantrip dot org
2024-01-04 11:46 ` rsandifo at gcc dot gnu.org [this message]

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-68703-4-bWIb7IXvnU@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).