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++/94569] alignas(object) with a weaker (smaller) alignment than the alignas(type) of it's type compiles, inconsistent with the C++ standard Date: Mon, 13 Apr 2020 01:25:19 +0000 [thread overview] Message-ID: <bug-94569-4-lShxn4H8GK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94569-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94569 Richard Smith <richard-gccbugzilla at metafoo dot co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard-gccbugzilla@metafoo | |.co.uk --- Comment #1 from Richard Smith <richard-gccbugzilla at metafoo dot co.uk> --- I believe the particular rule that is violated by this example is [dcl.align]p5: "The combined effect of all alignment-specifiers in a declaration shall not specify an alignment that is less strict than the alignment that would be required for the entity being declared if all alignment-specifiers appertaining to that entity were omitted."
next prev parent reply other threads:[~2020-04-13 1:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-12 20:34 [Bug c++/94569] New: " sinbal2l at gmail dot com 2020-04-13 1:25 ` richard-gccbugzilla at metafoo dot co.uk [this message] 2020-04-13 2:19 ` [Bug c++/94569] " sinbal2l at gmail dot com 2020-04-14 7:00 ` rguenth at gcc dot gnu.org 2020-04-14 7:32 ` richard-gccbugzilla at metafoo dot co.uk 2020-04-14 10:46 ` redi at gcc dot gnu.org 2020-05-10 6:29 ` sinbal2l at gmail dot com 2020-07-02 8:47 ` redi at gcc dot gnu.org 2020-07-02 10:25 ` sinbal2l at gmail dot com 2020-07-02 10:33 ` sinbal2l at gmail dot com 2020-07-02 13:06 ` redi at gcc dot gnu.org 2020-07-02 14:35 ` sinbal2l at gmail dot com
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-94569-4-lShxn4H8GK@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).