From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13456 invoked by alias); 7 Feb 2008 15:55:07 -0000 Received: (qmail 12865 invoked by uid 48); 7 Feb 2008 15:54:24 -0000 Date: Thu, 07 Feb 2008 15:55:00 -0000 Message-ID: <20080207155424.12864.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libfortran/35063] [Regression wrt g77] I/O leaks handles/memory on Windows XP In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "Jerry_V_DeLisle at rl dot gov" 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: 2008-02/txt/msg00849.txt.bz2 ------- Comment #19 from Jerry_V_DeLisle at rl dot gov 2008-02-07 15:54 ------- Writing to an internal unit is nothing more than a fancy (formatted) assignment. Each thread allocates its own unit structure. Its not like file I/O where threads are accessing a common shared resource. I should mention that Danny Smith has sent me a potential patch that I will test tonight or tomorrow. I would not mind seeing a threaded example where this could be tested and that confirms we need to lock internal units. :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063