[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-07-19 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #19 from Steve Kargl --- On Sun, Jul 19, 2020 at 02:42:24PM +, arjen.markus895 at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 > > --- Comment #17 from Arjen Markus --- > As UMASK has two arguments,

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-07-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 Thomas Koenig changed: What|Removed |Added CC||tkoenig at gcc dot gnu.org --- Comment #

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-07-19 Thread arjen.markus895 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #17 from Arjen Markus --- As UMASK has two arguments, should it be possible to combine integer arguments of different kinds? That is: integer(kind=1) :: mask integer(kind=8) :: old call umask( mask, old ) (Probably a bit overdoing

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-07-19 Thread arjen.markus895 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #16 from Arjen Markus --- To get more involved in gfortran, I thought this issue might be a good starting point (it is the first of a number that Steve Kargl posted some time ago for this purpose). I added a small test program to chec

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-07-19 Thread arjen.markus895 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 Arjen Markus changed: What|Removed |Added CC||arjen.markus895 at gmail dot com --- Com

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-06-20 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #14 from Steve Kargl --- This patch brings UNLINK subroutine into agreement with its documentation. Index: gcc/fortran/check.c === --- gcc/fortran/check.c (revision 2801

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-06-20 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #13 from kargl at gcc dot gnu.org --- This patch makes the UMASK subroutine a generic subprogram. This is accomplished by converting its arguments to INTEGER(4), call _gfortran_umask_i4_sub, and converting the OLD argument back to an

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-06-20 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #12 from kargl at gcc dot gnu.org --- This makes the UMASK intrinsic function generic by converting the input argument to default integer kind and calling the relevant libgfortran function. Index: gcc/fortran/iresolve.c ==

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-06-20 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #11 from kargl at gcc dot gnu.org --- (In reply to kargl from comment #10) > The non-standard SLEEP intrinsic subroutine is documented as taking a > default integer argument. This patch enforces this restriction. > > Index: gcc/fortr

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2020-06-20 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- C

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2018-03-11 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 --- Comment #9 from kargl at gcc dot gnu.org --- KILL has been at least reviewed for correctness. See r258436 | kargl | 2018-03-11 14:34:40 -0700 (Sun, 11 Mar 2018) | 14 lines 2018-03-11 Steven G. Kargl * check.c (gfc_check_kill):

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2018-03-11 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30372 kargl at gcc dot gnu.org changed: What|Removed |Added Priority|P3 |P4 CC|

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2007-02-23 Thread sgk at troutmask dot apl dot washington dot edu
--- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2007-02-23 21:02 --- Subject: Re: various intrinsics do not diagnose invalid argument kinds On Fri, Feb 23, 2007 at 08:42:03PM -, burnus at gcc dot gnu dot org wrote: > > > > various intrinsics do not diagnose i

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2007-02-23 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2007-02-23 20:42 --- > various intrinsics do not diagnose invalid argument kinds The question is what is the right solution: a) Only allow certain kinds b) Allowing all kinds and doing the conversion/providing the needed functions. (a) i

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2007-02-11 Thread kargl at gcc dot gnu dot org
--- Comment #6 from kargl at gcc dot gnu dot org 2007-02-11 22:26 --- daniel, It's just an inconsistency in implementations. First, note that FX and myself implemented a lot of the g77 intrinsics procedures as our first foray into gfortran, so we may have missed some of the finer deta

[Bug fortran/30372] various intrinsics do not diagnose invalid argument kinds

2007-02-11 Thread dfranke at gcc dot gnu dot org
--- Comment #5 from dfranke at gcc dot gnu dot org 2007-02-11 21:51 --- Also affected: chmod, exit, getcwd, hostnm, link, rename, sleep, system_clock, unlink, umask (maybe others). SYSTEM_CLOCK accepts INTEGER(1) if exactly one or all of its optional arguments are of that type. UMASK(