public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109654] New: unnecessary "cannot bind packed field to reference" error when referenced type has aligned(1) attribute Date: Thu, 27 Apr 2023 20:03:18 +0000 [thread overview] Message-ID: <bug-109654-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109654 Bug ID: 109654 Summary: unnecessary "cannot bind packed field to reference" error when referenced type has aligned(1) attribute Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: richard-gccbugzilla at metafoo dot co.uk Target Milestone: --- As a workaround for people hitting #36566, I think GCC should accept cases like this: typedef __attribute__((aligned(1))) int packed_int; struct __attribute__((packed)) Foo { int i; packed_int& get() { return i; } }; Unfortunately GCC rejects: <source>:5:32: error: cannot bind packed field '((Foo*)this)->Foo::i' to 'packed_int&' {aka 'int&'} 5 | packed_int& get() { return i; } | And conversely, GCC accepts this code, which has a genuine misalignment issue: typedef __attribute__((aligned(1))) int packed_int; struct __attribute__((packed)) Foo { packed_int i; int& get() { return i; } }; I wonder if the check is mistakenly looking at the alignment of the source type instead of the alignment of the referent of the reference type?
next reply other threads:[~2023-04-27 20:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-27 20:03 richard-gccbugzilla at metafoo dot co.uk [this message] 2023-04-27 20:14 ` [Bug c++/109654] " pinskia at gcc dot gnu.org 2023-04-28 21:09 ` richard-gccbugzilla at metafoo dot co.uk 2023-05-12 20:49 ` 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-109654-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).