public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65211] Type alignment lost inside templated function
Date: Sun, 05 Dec 2021 06:45:06 +0000	[thread overview]
Message-ID: <bug-65211-4-MX77Jr9BTe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65211-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-12-05
     Ever confirmed|0                           |1

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, simplified testcase:
typedef unsigned v4ui __attribute__ ((vector_size(16), aligned (16)));
typedef unsigned v4ui_unaligned __attribute__ ((vector_size (16), aligned
(4)));
template<int I>
static v4ui t(unsigned *dest_data)
{
    return ((const v4ui_unaligned*)dest_data)[0];
}
template<int I>
static v4ui t1(unsigned *dest_data)
{
    typedef unsigned v4ui_1 __attribute__ ((vector_size (16), aligned (4)));
    return ((const v4ui_1*)dest_data)[0];
}
v4ui g(unsigned int *array)
{
    return t<1>(array+7);
}
v4ui f(unsigned int *array)
{
    return t1<1>(array+7);
}

Still a bug on the trunk even.

  parent reply	other threads:[~2021-12-05  6:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 16:47 [Bug c++/65211] New: " linux at carewolf dot com
2015-02-25 16:49 ` [Bug c++/65211] " linux at carewolf dot com
2015-02-25 16:51 ` linux at carewolf dot com
2015-02-25 17:08 ` linux at carewolf dot com
2015-02-25 17:24 ` linux at carewolf dot com
2021-12-05  6:45 ` pinskia at gcc dot gnu.org [this message]
2021-12-05  6:56 ` [Bug c++/65211] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-17 15:19 ` rguenth at gcc dot gnu.org
2022-04-14  1:58 ` jason at gcc dot gnu.org
2022-04-14  2:56 ` cvs-commit at gcc dot gnu.org
2022-04-26  7:54 ` [Bug c++/65211] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-05-13 16:28 ` cvs-commit at gcc dot gnu.org
2022-05-13 17:14 ` [Bug c++/65211] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-13 17:42 ` [Bug c++/65211] [9 " cvs-commit at gcc dot gnu.org
2022-05-13 17:59 ` jason 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-65211-4-MX77Jr9BTe@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).