public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25020]  New: NAG extension: module F90_UNIX providing access to UNIX functions (abort ...)
Date: Thu, 24 Nov 2005 15:54:00 -0000	[thread overview]
Message-ID: <bug-25020-6318@http.gcc.gnu.org/bugzilla/> (raw)

Hi,

it would be nice if gfortran implemented a facility like
NAG's F90_UNIX module.  The program

implicit none
call abort ()
end

compiles and links with gfc -std=gnu but not with -std=f95

With the NAG compiler one can write

USE f90_unix, ONLY: abort
implicit none
call abort ()
end

have access to the intrinsics and be happy.

See

http://www.nag.co.uk/nagware/np/r50_doc/nag_modules.html
http://www.nag.co.uk/nagware/np/r50_doc/f90_unix.html

for details.

Cheers,
-ha


-- 
           Summary: NAG extension: module F90_UNIX providing access to UNIX
                    functions (abort ...)
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: anlauf at gmx dot de
  GCC host triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2005-11-24 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 15:54 anlauf at gmx dot de [this message]
2005-11-26  3:26 ` [Bug fortran/25020] " pinskia at gcc dot gnu dot org
2005-12-20  8:29 ` anlauf at gmx dot de
2006-10-30 12:18 ` fxcoudert at gcc dot gnu dot org
2007-01-14 11:02 ` fxcoudert at gcc dot gnu dot org
2007-02-16 16:05 ` fxcoudert 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=bug-25020-6318@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).