public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114634] [11/12/13/14 Regression] Crash Issue Encountered in GCC Compilation of Template Code with Aligned Attribute Date: Mon, 08 Apr 2024 19:22:40 +0000 [thread overview] Message-ID: <bug-114634-4-J26KAeY6VS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114634-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114634 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |8.5.0 Target Milestone|--- |11.5 Summary|Crash Issue Encountered in |[11/12/13/14 Regression] |GCC Compilation of Template |Crash Issue Encountered in |Code with Aligned Attribute |GCC Compilation of Template | |Code with Aligned Attribute Keywords|ice-on-valid-code |ice-on-invalid-code Known to fail| |9.1.0 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So GCC 8.5.0 and before we rejected this code: ``` <source>:5:10: error: alignment may not be specified for 'e' enum { e __attribute__ ((aligned(16))) }; ^ ``` And GCC trunk rejects it if not inside a template struct so changing ice-on-valid to ice-on-invalid and marking it as a regression. Note clang accepts it in both cases though. But this is a gcc extension after all.
next prev parent reply other threads:[~2024-04-08 19:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-08 9:25 [Bug c/114634] New: " iamanonymous.cs at gmail dot com 2024-04-08 9:31 ` [Bug c++/114634] " rguenth at gcc dot gnu.org 2024-04-08 19:22 ` pinskia at gcc dot gnu.org [this message] 2024-04-12 13:33 ` [Bug c++/114634] [11/12/13/14 Regression] " law at gcc dot gnu.org 2024-04-12 14:01 ` [Bug c++/114634] [11/12/13/14 Regression] Crash Issue Encountered in GCC Compilation of Template Code with Aligned Attribute since r9-1745 jakub at gcc dot gnu.org 2024-04-12 16:34 ` jakub at gcc dot gnu.org 2024-04-17 12:56 ` [Bug c++/114634] [11/12/13 " jakub at gcc dot gnu.org 2024-04-21 4:09 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:44 ` [Bug c++/114634] [11/12 " jakub 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-114634-4-J26KAeY6VS@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).