public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnu.0kn at gishpuppy dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54923] Internal unit I/O error when using -malign-double
Date: Wed, 31 Oct 2012 03:55:00 -0000	[thread overview]
Message-ID: <bug-54923-4-uzHJI4DgY4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54923-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from Drew <gnu.0kn at gishpuppy dot com> 2012-10-31 03:54:56 UTC ---
After some googling I have found that ABI means application binary interface
and how this affects the problem, thank you.

I would be happy if someone could direct me to a tutorial on how to maintain
two different ABIs on the same machine (so as not to break unaligned code
elsewhere) and how to obtain it precompiled from a package maintainer.

As another workaround, it has been indicated that $LD_PRELOAD may be used to
link to an aligned malloc

http://gcc.gnu.org/ml/fortran/2007-08/msg00320.html

For information on how to do either I, and I'm sure many others attempting to
call SSE functions or DMA transfers from 32 bit gfortran, would be very
thankful.


      parent reply	other threads:[~2012-10-31  3:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-13 23:35 [Bug fortran/54923] New: " gnu.0kn at gishpuppy dot com
2012-10-14  2:53 ` [Bug fortran/54923] " kargl at gcc dot gnu.org
2012-10-14  4:35 ` dominiq at lps dot ens.fr
2012-10-31  3:55 ` gnu.0kn at gishpuppy dot com [this message]

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=bug-54923-4-uzHJI4DgY4@http.gcc.gnu.org/bugzilla/ \
    --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).