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: Mon, 20 Oct 2008 15:04:00 -0000	[thread overview]
Message-ID: <20081020150251.23917.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37839-3107@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from sje at cup dot hp dot com  2008-10-20 15:02 -------
With respect to comment #5, the problem isn't changing the library side.  It is
changing the compiler side.  The compiler, as near as I can tell, doesn't
declare the structure the way the library does but builds offsets based on the
type information in ioparm.def.  Is is these offsets that need to change and
ioparm.def can't be ifdef'ed as is.  We would need to add an explicit
preprocessing of the file or add code to the compiler to adjust the offsets
after creating them from ioparm.def


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37839


  parent reply	other threads:[~2008-10-20 15:04 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 [this message]
2008-10-28 18:28 ` sje at cup dot hp dot com
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=20081020150251.23917.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).