public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/100935] d: T.alignof ignores explicit align(N) type alignment Date: Wed, 09 Jun 2021 18:04:21 +0000 [thread overview] Message-ID: <bug-100935-4-z4zx9RakaR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100935-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100935 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:fe555102dc224b4d946becc8a9db514ecec66161 commit r9-9575-gfe555102dc224b4d946becc8a9db514ecec66161 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Wed Jun 9 19:37:22 2021 +0200 d: Respect explicit align(N) type alignment (PR100935) It was previously the natural type alignment, defined as the maximum of the field alignments for an aggregate. Make sure an explicit align(N) overrides it. gcc/d/ChangeLog: PR d/100935 * dmd/mtype.c (Type::getProperty): Prefer explicit alignment over natural alignment for alignof property. gcc/testsuite/ChangeLog: PR d/100935 * gdc.test/compilable/aggr_alignment.d: Add test cases. (cherry picked from commit 3ba036dd1a752d29764ad44adca6e68bec9599fe)
next prev parent reply other threads:[~2021-06-09 18:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-06 21:16 [Bug d/100935] New: " ibuclaw at gdcproject dot org 2021-06-09 18:00 ` [Bug d/100935] " cvs-commit at gcc dot gnu.org 2021-06-09 18:01 ` cvs-commit at gcc dot gnu.org 2021-06-09 18:03 ` cvs-commit at gcc dot gnu.org 2021-06-09 18:04 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-09 18:06 ` ibuclaw at gdcproject dot 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-100935-4-z4zx9RakaR@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).