public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "p dot w dot draper at durham dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/23060] New: %VAL construct not implemented
Date: Mon, 25 Jul 2005 15:28:00 -0000	[thread overview]
Message-ID: <20050725152615.23060.p.w.draper@durham.ac.uk> (raw)

The %VAL construct is used for passing arguments by value, rather than the 
usual by reference or descriptor. It is vital for interoperability with other
languages such as C.

This feature is available in g77:

http://gcc.gnu.org/onlinedocs/gcc-3.4.4/g77/_0025VAL_0028_0029.html#_0025VAL_0028_0029

My interest in this feature comes from the world of astronomy where we have
a large legacy code base (~1 Million SLOC) written in Fortran 77, (see
http://cvsweb.starlink.ac.uk) where this feature is used for efficiently
accessing large data arrays using mmap, complex data structures, and for
accessing dynamic memory.

-- 
           Summary: %VAL construct not implemented
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: p dot w dot draper at durham dot ac dot uk
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: i386-redhat-linux


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


             reply	other threads:[~2005-07-25 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 15:28 p dot w dot draper at durham dot ac dot uk [this message]
2005-07-25 15:40 ` [Bug fortran/23060] " pinskia at gcc dot gnu dot org
2005-07-25 16:00 ` pinskia at gcc dot gnu dot org
2005-07-25 16:44 ` pinskia at gcc dot gnu dot org
2005-07-25 16:57 ` 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=20050725152615.23060.p.w.draper@durham.ac.uk \
    --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).