public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Mon, 03 Aug 2020 08:49:08 +0000 [thread overview] Message-ID: <bug-96377-4-mrqyBeQ8wW@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 #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:a216daaa30bc8949086a16e7656f2025b692d03c commit r10-8562-ga216daaa30bc8949086a16e7656f2025b692d03c Author: Richard Sandiford <richard.sandiford@arm.com> Date: Mon Aug 3 09:48:36 2020 +0100 c: Fix bogus vector initialisation error [PR96377] One of the problems in this PR was that if we had: vector_type1 array[] = { vector_value1 }; process_init_element would only treat vector_value1 as initialising a vector_type1 if they had the same TYPE_MAIN_VARIANT. This has several problems: (1) It gives confusing error messages if the vector types are incompatible. (Tested by gcc.dg/pr96377-1.c.) (2) It means that we reject code that should be valid with -flax-vector-conversions. (Tested by gcc.dg/pr96377-2.c.) (3) On arm and aarch64 targets, it means that we reject some initializers that mix Advanced SIMD and standard GNU vectors. These vectors have traditionally had different TYPE_MAIN_VARIANTs because they have different mangling schemes. (Tested by gcc.dg/pr96377-[3-6].c.) (4) It means that we reject SVE initializers that should be valid. (Tested by gcc.target/aarch64/sve/gnu_vectors_[34].c.) (5) After r11-1741-g:31427b974ed7b7dd54e2 we reject: arm_neon_type1 array[] = { k ^ arm_neon_value1 }; because applying the binary operator to arm_neon_value1 strips the "Advanced SIMD type" attributes that were added in that patch. Stripping the attributes is problematic for other reasons though, so that still needs to be fixed separately. g++.target/aarch64/sve/gnu_vectors_[34].C already pass. gcc/c/ PR c/96377 * c-typeck.c (process_init_element): Split test for whether to recurse into a record, union or array into... (initialize_elementwise_p): ...this new function. Don't recurse into a vector type if the initialization value is also a vector. gcc/testsuite/ PR c/96377 * gcc.dg/pr96377-1.c: New test. * gcc.dg/pr96377-2.c: Likewise. * gcc.dg/pr96377-3.c: Likewise. * gcc.dg/pr96377-4.c: Likewise. * gcc.dg/pr96377-5.c: Likewise. * gcc.dg/pr96377-6.c: Likewise. * gcc.target/aarch64/pr96377-1.c: Likewise. * gcc.target/aarch64/sve/acle/general-c/gnu_vectors_3.c: Likewise. * gcc.target/aarch64/sve/acle/general-c/gnu_vectors_4.c: Likewise. * g++.target/aarch64/sve/acle/general-c++/gnu_vectors_3.C: Likewise. * g++.target/aarch64/sve/acle/general-c++/gnu_vectors_4.C: Likewise. (cherry picked from commit 7d599ad27b9bcf5165f87710f1abc64bbabd06ae)
next prev parent reply other threads:[~2020-08-03 8:49 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 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 [this message] 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-mrqyBeQ8wW@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: linkBe 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).