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] New: Internal unit I/O error when using -malign-double
Date: Sat, 13 Oct 2012 23:35:00 -0000	[thread overview]
Message-ID: <bug-54923-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 54923
           Summary: Internal unit I/O error when using -malign-double
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gnu.0kn@gishpuppy.com


Reading from of integer from character string fails with 
Fortran runtime error: Internal unit I/O error
when compiling with -malign-double.

Background: This occurred when using the usual getarg(1,arg) construct and
linking against FFTW3, which requires data alignment.

Minimal example:
___

      PROGRAM readtest
      IMPLICIT NONE

      CHARACTER*8 arg
      INTEGER inputarg

      arg=" 1 "
      READ(arg,*) inputarg
      PRINT *,"Argument supplied was: ", inputarg

      RETURN
      END
___

Compiling with gfortran without data alignment yields the expected result.
Compiling with -malign-double in the compiler options yields runtime error.

Thank you.


             reply	other threads:[~2012-10-13 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-13 23:35 gnu.0kn at gishpuppy dot com [this message]
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

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@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).