public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "orion at cora dot nwra.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64416] New: RFE: Support REAL128 on arm
Date: Fri, 26 Dec 2014 23:25:00 -0000	[thread overview]
Message-ID: <bug-64416-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64416

            Bug ID: 64416
           Summary: RFE: Support REAL128 on arm
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: orion at cora dot nwra.com

SUBROUTINE PMPI_Sizeof_complex128_scalar(x, size, ierror)
        USE, INTRINSIC :: iso_fortran_env, ONLY: REAL128
      COMPLEX(REAL128)::x
        INTEGER, INTENT(OUT) :: size
        INTEGER, INTENT(OUT) :: ierror

        size = storage_size(x) / 8
        ierror = 0
      END SUBROUTINE PMPI_Sizeof_complex128_scalar

gfortran -c psizeof_f.f90 
psizeof_f.f90:3.21:

      COMPLEX(REAL128)::x
                     1
Error: Kind -1 not supported for type COMPLEX at (1)

Linux fedora-rawhide-arm 3.18.1-2.fc22.armv7hl+lpae #1 SMP Fri Dec 19 00:19:30
UTC 2014 armv7l armv7l armv7l GNU/Linux

Is it possible to add support for this, or can the architecture not handle it?


             reply	other threads:[~2014-12-26 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 23:25 orion at cora dot nwra.com [this message]
2014-12-30 21:20 ` [Bug fortran/64416] " joseph at codesourcery dot com
2015-01-15 14:34 ` rearnsha at gcc dot gnu.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=bug-64416-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).