From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14637 invoked by alias); 16 Apr 2007 12:32:00 -0000 Received: (qmail 14575 invoked by uid 48); 16 Apr 2007 12:31:48 -0000 Date: Mon, 16 Apr 2007 12:32:00 -0000 Message-ID: <20070416123148.14574.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/31587] Module files shouldn't be updated if their content doesn't change In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "tobi 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-04/txt/msg01125.txt.bz2 ------- Comment #2 from tobi at gcc dot gnu dot org 2007-04-16 13:31 ------- Given your other PR, another solution that comes to mind is to include the filename and modification date of the source file in the module file, and to compare these before writing a module file. This would be more prone to inconsistencies than the approach from comment #1, as it wouldn't actually be verified that the .mod file remains unchanged. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31587