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/109762] [12/13 Regression] gcc/config/aarch64/aarch64-builtins.cc: mismatched sizes for flags variables Date: Sun, 07 May 2023 20:17:34 +0000 [thread overview] Message-ID: <bug-109762-4-FM833od4d9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109762-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109762 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:fc79c3a273a8fd7c1b57cd8b01a699ad2640f51c commit r13-7304-gfc79c3a273a8fd7c1b57cd8b01a699ad2640f51c Author: Andrew Pinski <apinski@marvell.com> Date: Sun May 7 01:38:17 2023 +0000 [GCC 13] Fix aarch64/109762: push_options/push_options does not work sometimes aarch64_isa_flags (and aarch64_asm_isa_flags) are both aarch64_feature_flags (uint64_t) but since r12-8000-g14814e20161d, they are saved/restored as unsigned long. This does not make a difference for LP64 targets but on ILP32 and LLP64IL32 targets, it means it does not get restored correctly. This patch changes over to use aarch64_feature_flags instead of unsigned long. Committed as obvious to gcc 13 branch after a bootstrap/test. gcc/ChangeLog: PR target/109762 * config/aarch64/aarch64-builtins.cc (aarch64_simd_switcher::aarch64_simd_switcher): Change argument type to aarch64_feature_flags. * config/aarch64/aarch64-protos.h (aarch64_simd_switcher): Change constructor argument type to aarch64_feature_flags. Change m_old_asm_isa_flags to be aarch64_feature_flags. (cherry picked from commit a1a9ce2441df0675540faee8476523164e12578b)
next prev parent reply other threads:[~2023-05-07 20:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-07 0:34 [Bug driver/109762] New: [AArch64] " davem at devkitpro dot org 2023-05-07 0:37 ` [Bug driver/109762] " davem at devkitpro dot org 2023-05-07 0:51 ` [Bug target/109762] " pinskia at gcc dot gnu.org 2023-05-07 1:30 ` [Bug target/109762] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-07 2:23 ` [Bug target/109762] [12/13/14 " pinskia at gcc dot gnu.org 2023-05-07 2:28 ` pinskia at gcc dot gnu.org 2023-05-07 2:45 ` pinskia at gcc dot gnu.org 2023-05-07 15:26 ` cvs-commit at gcc dot gnu.org 2023-05-07 15:28 ` [Bug target/109762] [12/13 " pinskia at gcc dot gnu.org 2023-05-07 20:17 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-07 20:23 ` [Bug target/109762] [12 " pinskia at gcc dot gnu.org 2024-05-08 16:13 ` pinskia 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-109762-4-FM833od4d9@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).