public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "macro at linux-mips dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/21937] [4.0 Regression] Member record alignment triggers an ICE Date: Tue, 07 Jun 2005 18:16:00 -0000 [thread overview] Message-ID: <20050607181648.22468.qmail@sourceware.org> (raw) In-Reply-To: <20050606204209.21937.macro@linux-mips.org> ------- Additional Comments From macro at linux-mips dot org 2005-06-07 18:16 ------- > > Of course it changes the ABI -- if any member of a record (which is an > > equivalent to a C structure) gets its alignment increased, then the alignment > > of the containing record (structure) gets adjusted appropriately. > > Sure, but since all records of this type will be laid out the same way, where is > the problem? This only happens for packed records or records with After a short consideration I agree -- it would only be a problem if the case was reversed, i.e. standalone records got their alignment bumped while member oned did not. > representation clauses, both not bound to any ABI rules as far as Ada is concerned. Well, there may be no written standard for this case, but there is always an ABI, even if limited to GCC. > > If I understand code correctly compute_record_mode() should still be able to > > use one of the integer modes for platforms that don't care about alignment. > > x86 is not (yet) the only platform out there. :-) Well, you may have noticed I'm already aware of this -- otherwise I wouldn't have filed the report in the first place. But the problem is the i386 is probably the architecture most code is primarily tested with and unfortunately it has quite forgiving restrictions about alignment. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21937
next prev parent reply other threads:[~2005-06-07 18:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-06 20:42 [Bug ada/21937] New: Member record alignment triggering " 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 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 ` macro at linux-mips dot org [this message] 2005-06-07 18:56 ` [Bug ada/21937] [4.0 Regression] Member record alignment triggers " 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=20050607181648.22468.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).