public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/21937] Member record alignment triggering an ICE Date: Tue, 07 Jun 2005 11:30:00 -0000 [thread overview] Message-ID: <20050607113036.13627.qmail@sourceware.org> (raw) In-Reply-To: <20050606204209.21937.macro@linux-mips.org> ------- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-06-07 11:30 ------- > This problem happens for platforms that set STRICT_ALIGNMENT. For them it is > possible for a given record type to be expressed using an integer mode if used > as a member record, and the BLK mode if used standalone. As a result an > assignment where lhs is BLKmode and rhs is *Imode may be generated and this > triggers an ICE. That's not quite true, the type is not the same. > I've been able to track the problem down to the alignment of member records > being increased implicitly in an attempt to fit them into an integer mode. > I believe it is incorrect as it changes the alignment of the containing > record as well and therefore it changes the ABI. How does that change the ABI for the containing record type? The type is laid out only once. As for members, this is only done for non-aliased members so ABI considerations are irrelevant. > 2005-06-07 Maciej W. Rozycki <macro@linux-mips.org> > > * ada/decl.c (make_packable_type): Use the same alignment for the new > type. That would defeat the purpose of make_packable_type. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-06-07 11:30:35 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21937
next prev parent reply other threads:[~2005-06-07 11:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-06 20:42 [Bug ada/21937] New: " macro at linux-mips dot org 2005-06-06 20:43 ` [Bug ada/21937] " macro at linux-mips dot org 2005-06-06 20:45 ` macro at linux-mips dot org 2005-06-06 21:07 ` pluto at agmk dot net 2005-06-06 21:20 ` pinskia at gcc dot gnu dot org 2005-06-07 10:29 ` macro at linux-mips dot org 2005-06-07 11:30 ` ebotcazou at gcc dot gnu dot org [this message] 2005-06-07 11:31 ` ebotcazou at gcc dot gnu dot org 2005-06-07 12:15 ` macro at linux-mips dot org 2005-06-07 12:16 ` ebotcazou at gcc dot gnu dot org 2005-06-07 12:26 ` ebotcazou at gcc dot gnu dot org 2005-06-07 18:16 ` [Bug ada/21937] [4.0 Regression] Member record alignment triggers " macro at linux-mips dot org 2005-06-07 18:56 ` ebotcazou at gcc dot gnu dot org 2005-09-06 8:26 ` [Bug ada/21937] [4.0/4.1 " ebotcazou at gcc dot gnu 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=20050607113036.13627.qmail@sourceware.org \ --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).