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 target/96377] [10/11 Regression] GCC 10.2/11 doesn't build Linux kernel anymore
Date: Thu, 30 Jul 2020 14:06:19 +0000	[thread overview]
Message-ID: <bug-96377-4-s9KVslLnYr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96377-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
I think this is bound up with the question whether:

typedef int v4si __attribute__((vector_size(16)));
typedef short v8hi __attribute__((vector_size(16)));

struct s {
  v8hi x;
  v4si y;
};

void
foo (v4si i, v8hi h)
{
  struct s x1 = { i, i };
  struct s x2 = { h, h };
  struct s x3 = { i, h };
  struct s x4 = { h, i };
}

should be valid with -flax-vector-conversions.  g++ and clang
think it should be, but gcc doesn't accept it.

IMO process_init_element shouldn't recurse into vector types
if the initialisation value is also a vector type.  We should
treat the vector value as initialising the whole type and report
an error if they're not compatible.

  parent reply	other threads:[~2020-07-30 14:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 16:04 [Bug target/96377] New: " jakub at gcc dot gnu.org
2020-07-29 16:04 ` [Bug target/96377] " jakub at gcc dot gnu.org
2020-07-29 16:18 ` jakub at gcc dot gnu.org
2020-07-29 16:40 ` jakub at gcc dot gnu.org
2020-07-29 16:48 ` jakub at gcc dot gnu.org
2020-07-29 17:40 ` rsandifo at gcc dot gnu.org
2020-07-30 14:06 ` rsandifo at gcc dot gnu.org [this message]
2020-07-30 14:09 ` rsandifo at gcc dot gnu.org
2020-07-30 15:41 ` jakub at gcc dot gnu.org
2020-07-30 15:58 ` rsandifo at gcc dot gnu.org
2020-07-30 17:08 ` rsandifo at gcc dot gnu.org
2020-07-30 19:55 ` joseph at codesourcery dot com
2020-08-01 11:42 ` cvs-commit at gcc dot gnu.org
2020-08-03  8:49 ` cvs-commit at gcc dot gnu.org
2020-09-10 17:21 ` rsandifo at gcc dot gnu.org
2020-11-18 14:33 ` jakub at gcc dot gnu.org
2020-11-18 16:56 ` rsandifo at gcc dot gnu.org
2021-01-27  9:28 ` 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-96377-4-s9KVslLnYr@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).