public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96377] New: [10/11 Regression] GCC 10.2/11 doesn't build Linux kernel anymore
Date: Wed, 29 Jul 2020 16:04:25 +0000 [thread overview]
Message-ID: <bug-96377-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377
Bug ID: 96377
Summary: [10/11 Regression] GCC 10.2/11 doesn't build Linux
kernel anymore
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
The following testcase reduced from Linux kernel's crypto/aegis128-neon-inner.c
started to be rejected with r11-1741-g31427b974ed7b7dd54e28fec595e731bf6eea8ba
and r10-8501-g932e9140d3268cf2033c1c3e93219541c53fcd29
#include <arm_neon.h>
struct aegis128_state {
uint8x16_t v[5];
};
void foo(const void *key, const void *iv, const void *const0, const void
*const1)
{
uint8x16_t k = vld1q_u8(key);
uint8x16_t kiv = k ^ vld1q_u8(iv);
struct aegis128_state st = {{
kiv,
vld1q_u8(const1),
vld1q_u8(const0),
k ^ vld1q_u8(const0),
k ^ vld1q_u8(const1),
}};
}
The error is:
error: incompatible types when initializing type ‘unsigned char’ using type
‘uint8x16_t’ {aka ‘__Uint8x16_t’}
(twice)
next reply other threads:[~2020-07-29 16:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 16:04 jakub at gcc dot gnu.org [this message]
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
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@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).