public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/37839] st_parameter_dt has unwanted padding, is out of sync with compiler
Date: Tue, 28 Oct 2008 18:28:00 -0000 [thread overview]
Message-ID: <20081028182657.16590.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37839-3107@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from sje at cup dot hp dot com 2008-10-28 18:26 -------
Further investigation shows that it is not the size of common that is the
problem. The bug is related to the new union of st_parameter_43 and
st_parameter_44. Specifically, st_parameter_44 contains pos which is type
GFC_IO_INT which is 8 bytes on IA64 and requires an 8 byte alignment. This
causes the entire st_parameter_44 structure to require 8 byte alignment and the
union that it is part of to require 8 byte alignment. This changes the
layout/offset of fields in the p and q parts of the st_parameter_dt structure.
The compiler definition of st_parameter_dt, created from ioparm.def, does not
know anything about the union that is used in the library and just lays out the
fields as if there was no *_44 structure and no union and this layout is then
different then the library layout.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37839
next prev parent reply other threads:[~2008-10-28 18:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 17:54 [Bug libfortran/37839] New: " sje at cup dot hp dot com
2008-10-15 23:10 ` [Bug libfortran/37839] " janis at gcc dot gnu dot org
2008-10-16 10:02 ` burnus at gcc dot gnu dot org
2008-10-16 15:24 ` sje at cup dot hp dot com
2008-10-16 15:33 ` dominiq at lps dot ens dot fr
2008-10-17 3:42 ` jvdelisle at gcc dot gnu dot org
2008-10-19 4:01 ` jvdelisle at gcc dot gnu dot org
2008-10-19 12:02 ` burnus at gcc dot gnu dot org
2008-10-20 15:04 ` sje at cup dot hp dot com
2008-10-28 18:28 ` sje at cup dot hp dot com [this message]
2008-11-01 12:18 ` jvdelisle at gcc dot gnu dot org
2008-11-06 14:04 ` dominiq at lps dot ens dot fr
2008-11-20 15:09 ` jakub at gcc dot gnu dot org
2008-11-21 12:44 ` howarth at nitro dot med dot uc dot edu
2008-11-21 12:45 ` jakub at gcc dot gnu dot org
2008-11-22 5:23 ` jvdelisle at gcc dot gnu dot org
2008-11-22 8:13 ` jakub at gcc dot gnu dot org
2008-11-22 8:32 ` jakub 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=20081028182657.16590.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: link
Be 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).