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++/104177] [diagnostic] basic.align#9 should emit diagnostic for unsupported alignas Date: Sat, 22 Jan 2022 02:22:53 +0000 [thread overview] Message-ID: <bug-104177-4-1aWjf1TdCA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104177-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104177 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- What I am trying to say is there is a bug in gcc when dealing with alignas with coroutines. I don't think there is a dup of this bug in the database. I am also saying is this should work. When I get in front of my computer next, I will to see if I can see something obviously going wrong. Also gcc does implement the full alignas up to a very big alignment. Though I remember seeing some other alignas bugs and I will find them and link them here.
next prev parent reply other threads:[~2022-01-22 2:22 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-22 1:59 [Bug c++/104177] New: " ldalessandro at gmail dot com 2022-01-22 2:02 ` [Bug c++/104177] " ldalessandro at gmail dot com 2022-01-22 2:04 ` pinskia at gcc dot gnu.org 2022-01-22 2:05 ` pinskia at gcc dot gnu.org 2022-01-22 2:07 ` ldalessandro at gmail dot com 2022-01-22 2:22 ` pinskia at gcc dot gnu.org [this message] 2022-01-22 3:48 ` pinskia at gcc dot gnu.org 2022-01-22 3:48 ` pinskia at gcc dot gnu.org 2022-01-22 4:08 ` [Bug c++/104177] coroutine frame is not being allocated with the correct alignment pinskia at gcc dot gnu.org 2022-01-22 4:14 ` pinskia at gcc dot gnu.org 2022-01-22 4:18 ` pinskia at gcc dot gnu.org 2022-01-22 4:19 ` pinskia at gcc dot gnu.org 2022-01-22 4:20 ` pinskia at gcc dot gnu.org 2022-01-28 20:49 ` iains at gcc dot gnu.org 2022-01-28 21:10 ` ldalessandro at gmail dot com 2023-01-21 6:50 ` davidledger at live dot com.au 2023-01-21 6:51 ` davidledger at live dot com.au 2023-01-23 7:30 ` pinskia at gcc dot gnu.org 2023-01-23 7:33 ` pinskia at gcc dot gnu.org 2023-01-23 7:39 ` pinskia at gcc dot gnu.org 2023-01-23 9:02 ` davidledger at live dot com.au 2023-08-10 7:37 ` pinskia at gcc dot gnu.org 2024-04-30 19:42 ` 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-104177-4-1aWjf1TdCA@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).