public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davem at devkitpro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/109762] New: [AArch64] gcc/config/aarch64/aarch64-builtins.cc: mismatched sizes for flags variables Date: Sun, 07 May 2023 00:34:36 +0000 [thread overview] Message-ID: <bug-109762-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109762 Bug ID: 109762 Summary: [AArch64] gcc/config/aarch64/aarch64-builtins.cc: mismatched sizes for flags variables Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: davem at devkitpro dot org Target Milestone: --- Created attachment 55013 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55013&action=edit preprocessed source that fails On windows and 32 bit hosts int and long are 32bit while aarch64_feature_flags is 64bit. This causes compilation failures on windows & 32bit hosts. The attached source fails with a spurious inlining failed in call to 'always_inline' 'unsigned int GetConstant()': target specific option mismatch.
next reply other threads:[~2023-05-07 0:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-07 0:34 davem at devkitpro dot org [this message] 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 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@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).