[Bug fortran/30941] intrinsic: FLUSH

2010-05-13 Thread dfranke at gcc dot gnu dot org 


--- Comment #4 from dfranke at gcc dot gnu dot org  2010-05-13 13:50 ---
This (a) didn't turn out as much of an issue and (b) the general problem is
known. Closing this specific incarnation as WONTFIX.


-- 

dfranke at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX


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

[Bug fortran/30941] intrinsic: FLUSH

2007-03-03 Thread fxcoudert at gcc dot gnu dot org 


--- Comment #3 from fxcoudert at gcc dot gnu dot org  2007-03-03 10:22 
---
For what it's worth, here's my opinion: we don't want to have a zillion of
different versions of each library function. It might be worth doing for
functions that are expected to be called in hot spots of the user code, but not
for FLUSH, EXIT and other such intrinsics. So, it would be better to agree once
and for all on a reasonnable choice of kind, depending on the use done for the
intrinsic, and implementing and documenting this.

I think in the case of FLUSH, there's an easy choice for the kind of UNIT. The
unit numbers are always, in the I/O library, of kind=4 (see libgfortran.h,
struct st_parameter_common).


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2007-03-03 10:22:38
   date||


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

[Bug fortran/30941] intrinsic: FLUSH

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


--- Comment #1 from dfranke at gcc dot gnu dot org  2007-02-23 22:28 ---
libgfortran/io/intrinsics.c provides flush_i8, but that one is never used. 

INTEGER(kind=8) :: i8
CALL FLUSH(i8)

results in 

MAIN__ ()
{
  int8 int_8;

  _gfortran_set_std (70, 127, 0, 0);
  {
int4 D.1001;

D.1001 = (int4) int_8;
_gfortran_flush_i4 (D.1001);
  }
}


-- 


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

[Bug fortran/30941] intrinsic: FLUSH

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


--- Comment #2 from dfranke at gcc dot gnu dot org  2007-02-23 22:58 ---
The problem described in comment #1 depends on the default integer kind.
See also: http://gcc.gnu.org/ml/fortran/2007-02/msg00542.html


-- 


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