[Bug fortran/30933] intrinsic: EXIT

2007-08-06 Thread fxcoudert at gcc dot gnu dot org


--- Comment #9 from fxcoudert at gcc dot gnu dot org  2007-08-06 22:29 
---
Subject: Bug 30933

Author: fxcoudert
Date: Mon Aug  6 22:29:24 2007
New Revision: 127256

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=127256
Log:
PR fortran/30933
* iresolve.c (gfc_resolve_exit): Convert argument to default
integer kind.

Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/iresolve.c


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-08-06 Thread fxcoudert at gcc dot gnu dot org


--- Comment #10 from fxcoudert at gcc dot gnu dot org  2007-08-06 22:29 
---
Last bit fixed.


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


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



[Bug fortran/30933] intrinsic: EXIT

2007-08-06 Thread fxcoudert at gcc dot gnu dot org


--- Comment #11 from fxcoudert at gcc dot gnu dot org  2007-08-06 22:44 
---
Subject: Bug 30933

Author: fxcoudert
Date: Mon Aug  6 22:44:27 2007
New Revision: 127257

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=127257
Log:
PR fortran/30933
* intrinsic.c (add_functions): Fix name of argument to CHDIR.

Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/intrinsic.c


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-03-31 Thread burnus at gcc dot gnu dot org


--- Comment #8 from burnus at gcc dot gnu dot org  2007-03-31 18:34 ---
Author: burnus
Date: Sat Mar 31 18:30:11 2007
New Revision: 123385

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=123385
Log:
2007-03-31  Tobias Burnus  [EMAIL PROTECTED]

   * intrinsic.c (add_functions): Fix name of dummy argument
 for new_line and exit intrinsic.

Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/intrinsic.c



The integer(1,2,16?) support (or rejection) needs still to be done.


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|burnus at gcc dot gnu dot   |unassigned at gcc dot gnu
   |org |dot org
 Status|ASSIGNED|NEW


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



[Bug fortran/30933] intrinsic: EXIT

2007-03-13 Thread brooks at gcc dot gnu dot org


--- Comment #6 from brooks at gcc dot gnu dot org  2007-03-14 04:45 ---
The above commit fixes the documentation to document that only default integer
arguments are allowed.

I left the argument name as STATUS, because COUNT seems absurd and in this
case I think it's clear that we want to fix the implementation.


-- 

brooks at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||brooks at gcc dot gnu dot
   ||org


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



[Bug fortran/30933] intrinsic: EXIT

2007-03-13 Thread brooks at gcc dot gnu dot org


--- Comment #7 from brooks at gcc dot gnu dot org  2007-03-14 04:47 ---
The above commit is obviously missing; I typoed the PR number when making it.
 Here's the info:

Author: brooks
Date: Wed Mar 14 04:38:47 2007
New Revision: 122905

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=122905
Log:
PR fortran/30922
PR fortran/30948
PR fortran/30953
* intrinsics.texi (CHDIR): Fix argument names, note
that STATUS must be a default integer.
(CTIME): Fix argument names, note that RESULT must
be a default integer.
(EXIT): Note that STATUS must be a default integer.

Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/intrinsic.texi


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-02-23 Thread burnus at gcc dot gnu dot org


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||burnus at gcc dot gnu dot
   ||org
 AssignedTo|unassigned at gcc dot gnu   |burnus at gcc dot gnu dot
   |dot org |org
 Status|UNCONFIRMED |ASSIGNED
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2007-02-23 16:45:28
   date||


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



[Bug fortran/30933] intrinsic: EXIT

2007-02-23 Thread patchapp at dberlin dot org


--- Comment #5 from patchapp at dberlin dot org  2007-02-23 18:05 ---
Subject: Bug number PR30933

A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-02/msg01902.html


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-02-22 Thread dfranke at gcc dot gnu dot org


--- Comment #1 from dfranke at gcc dot gnu dot org  2007-02-22 23:40 ---
Created an attachment (id=13093)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13093action=view)
testcase (dg-do compile)


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-02-22 Thread dfranke at gcc dot gnu dot org


--- Comment #2 from dfranke at gcc dot gnu dot org  2007-02-22 23:40 ---
Created an attachment (id=13094)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13094action=view)
testcase (dg-do link)


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-02-22 Thread dfranke at gcc dot gnu dot org


--- Comment #3 from dfranke at gcc dot gnu dot org  2007-02-23 00:21 ---
A note on the testcase: gfortran seems to resolve EXIT only once. 
If
  CALL exit()
  CALL exit(int_1)
gfortran happily compiles and links.

If 
  CALL exit(int_1)
  CALL exit()
then
/tmp/ccuE9OGi.o: In function `MAIN__':
subroutine-exit-link.f90:(.text+0x31): undefined reference to
`_gfortran_exit_i1'
collect2: ld returned 1 exit status

The same goes for `_gfortran_exit_i2':
if
  CALL exit(int_1)
  CALL exit(int_2)
then only `_gfortran_exit_i1' is missing -- and vice versa.


-- 


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



[Bug fortran/30933] intrinsic: EXIT

2007-02-22 Thread dfranke at gcc dot gnu dot org


--- Comment #4 from dfranke at gcc dot gnu dot org  2007-02-23 00:38 ---
The documentation states:

 Arguments:
   STATUS   The type of the argument shall be INTEGER(*). 

but arguments of kind INTEGER(kind=1) and INTEGER(kind=2) may lead to
unresolved symbols (see also comment #3).


-- 

dfranke at gcc dot gnu dot org changed:

   What|Removed |Added

   Keywords||documentation


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