public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30948]  New: intrinsic: CHDIR
Date: Sat, 24 Feb 2007 18:48:00 -0000	[thread overview]
Message-ID: <bug-30948-13648@http.gcc.gnu.org/bugzilla/> (raw)

subroutine = {
        name = 'chdir';
        arg  = 'path';
        arg  = 'status';

        call = 'CALL chdir(path = string)';
        call = 'CALL chdir(path = string, status = int_1)';
        call = 'CALL chdir(path = string, status = int_2)';
        call = 'CALL chdir(path = string, status = int_4)';
        call = 'CALL chdir(path = string, status = int_8)';
};

1. The name of the first dummy argument is "NAME" instead of "PATH" (as
documented)
2. The library does not provide overloads for int1 and int2 (i16?)
3. The documentation does not specify the type of the STATUS argument


-- 
           Summary: intrinsic: CHDIR
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: rejects-valid, documentation
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dfranke at gcc dot gnu dot org
OtherBugsDependingO 30932
             nThis:


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


             reply	other threads:[~2007-02-24 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 18:48 dfranke at gcc dot gnu dot org [this message]
2007-02-24 18:55 ` [Bug fortran/30948] " dfranke at gcc dot gnu dot org
2007-03-03 10:23 ` fxcoudert at gcc dot gnu dot org
2007-03-14  4:19 ` brooks at gcc dot gnu dot org
2007-03-14  4:37 ` brooks at gcc dot gnu dot org
2007-03-14  4:39 ` brooks at gcc dot gnu dot org
2007-03-14  4:44 ` brooks at gcc dot gnu dot org
2007-08-06 22:46 ` 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-30948-13648@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).