public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jblomqvi at cc dot hut dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/24174] real(10) array output broken
Date: Sun, 09 Oct 2005 20:52:00 -0000	[thread overview]
Message-ID: <20051009205212.3686.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24174-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from jblomqvi at cc dot hut dot fi  2005-10-09 20:52 -------
(In reply to comment #5)
> > It should be noted that the patch assumes that the padding for real(10) is 10
> > bytes data + 2 bytes padding. This works on i686-Linux, might not work on other
> > targets (big endian?).
> 
> Itanium has padding to 16 bytes for 10-byte reals.
> 
> Using 12 bytes for 10-byte reals on ia686 would mean breaking binary
> compatibility with Itanium :-(

Indeed, looking at
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
it seems that x86-64 also pads real(10) to 16 bytes. See the doc for the
-m128bit-long-double switch.


-- 

jblomqvi at cc dot hut dot fi changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


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


  parent reply	other threads:[~2005-10-09 20:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03  9:16 [Bug libfortran/24174] New: " fxcoudert at gcc dot gnu dot org
2005-10-03  9:39 ` [Bug libfortran/24174] " jblomqvi at cc dot hut dot fi
2005-10-03 10:37 ` fxcoudert at gcc dot gnu dot org
2005-10-03 19:37 ` jblomqvi at cc dot hut dot fi
2005-10-03 19:40 ` jblomqvi at cc dot hut dot fi
2005-10-07 20:12 ` tkoenig at gcc dot gnu dot org
2005-10-09 19:36 ` jblomqvi at cc dot hut dot fi
2005-10-09 20:52 ` jblomqvi at cc dot hut dot fi [this message]
2005-10-09 21:29 ` jblomqvi at cc dot hut dot fi
2005-10-11  6:11 ` jblomqvi at cc dot hut dot fi
2005-11-05 18:07 ` jblomqvi at cc dot hut dot fi
2005-11-06 18:28 ` jb at gcc dot gnu dot org
2005-11-11 20:46 ` jb at gcc dot gnu dot org
2005-11-13  6:31 ` pinskia 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=20051009205212.3686.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).