From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26398 invoked by alias); 3 Mar 2007 10:22:50 -0000 Received: (qmail 26352 invoked by uid 48); 3 Mar 2007 10:22:39 -0000 Date: Sat, 03 Mar 2007 10:22:00 -0000 Message-ID: <20070303102239.26351.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/30941] intrinsic: FLUSH In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "fxcoudert at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-03/txt/msg00154.txt.bz2 ------- 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|0000-00-00 00:00:00 |2007-03-03 10:22:38 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30941