From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14738 invoked by alias); 19 May 2007 10:22:42 -0000 Received: (qmail 14678 invoked by alias); 19 May 2007 10:22:32 -0000 Date: Sat, 19 May 2007 10:22:00 -0000 Message-ID: <20070519102232.14677.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/20373] INTRINSIC symbols can be given the wrong type In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" 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-05/txt/msg01527.txt.bz2 ------- Comment #9 from Tobias dot Schlueter at physik dot uni-muenchen dot de 2007-05-19 11:22 ------- Subject: Re: INTRINSIC symbols can be given the wrong type dfranke at gcc dot gnu dot org wrote: > Thus, we should make sure that each intrinsic starts with the correct type to > begin with and emit a warning/error if someone attempts to change that type > (wherever the right place for this may be)? The idea is probably that giving all intrinsics types right from the beginning would be unnecessarily blowing up namespaces, and therefore memory and compile-time consumption (and maybe module files) What one can possibly do, though it might require quite a bit of care, is modifying variable_decl() to check if the symbol is an intrinsic declared with the correct type before adding it to the namespace. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20373