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/30372] kill intrinsic doesn't diagnose invalid argument kinds
Date: Sun, 11 Feb 2007 19:39:00 -0000	[thread overview]
Message-ID: <20070211193933.24794.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30372-13350@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from dfranke at gcc dot gnu dot org  2007-02-11 19:39 -------
Contrary to this, the docs of g77-3.4.6 [1] state:
    Status: INTEGER(KIND=1); OPTIONAL; scalar; INTENT(OUT). 

Also, the comment at the beginning of libgfortran/intrinsics/kill.c [2] states:
/* SUBROUTINE KILL(PID, SIGNAL, STATUS)
   INTEGER, INTENT(IN) :: PID, SIGNAL
   INTEGER(KIND=1), INTENT(OUT), OPTIONAL :: STATUS

   INTEGER(KIND=1) FUNCTION KILL(PID, SIGNAL)
   INTEGER, INTENT(IN) :: PID, SIGNAL */

Thus, maybe libgfortran should provide `_gfortran_kill_i1_sub'?


[1]
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/Kill-Intrinsic-_0028subroutine_0029.html
[2] http://gcc.gnu.org/viewcvs/trunk/libgfortran/intrinsics/kill.c?view=markup


-- 

dfranke at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dfranke at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2007-02-11 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 20:33 [Bug fortran/30372] New: " brooks at gcc dot gnu dot org
2007-01-23 15:17 ` [Bug fortran/30372] " fxcoudert at gcc dot gnu dot org
2007-02-11 19:39 ` dfranke at gcc dot gnu dot org [this message]
2007-02-11 20:43 ` kargl at gcc dot gnu dot org
2007-02-11 21:02 ` dfranke at gcc dot gnu dot org
2007-02-11 21:52 ` [Bug fortran/30372] various intrinsics do not " dfranke at gcc dot gnu dot org
2007-02-11 22:26 ` kargl at gcc dot gnu dot org
2007-02-23 20:42 ` burnus at gcc dot gnu dot org
2007-02-23 21:02 ` sgk at troutmask dot apl dot washington dot edu

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=20070211193933.24794.qmail@sourceware.org \
    --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).