From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5616 invoked by alias); 9 Mar 2005 16:01:59 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 5484 invoked by uid 48); 9 Mar 2005 16:01:52 -0000 Date: Wed, 09 Mar 2005 16:01:00 -0000 Message-ID: <20050309160152.5483.qmail@sourceware.org> From: "Thomas dot Koenig at online dot de" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050304195657.20323.tow21@cam.ac.uk> References: <20050304195657.20323.tow21@cam.ac.uk> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug fortran/20323] optional arguments incorrectly accepted in specification expressions X-Bugzilla-Reason: CC X-SW-Source: 2005-03/txt/msg01173.txt.bz2 List-Id: ------- Additional Comments From Thomas dot Koenig at online dot de 2005-03-09 16:01 ------- The complaint is a segfault at runtime when you actually want to do anything with the string whose length depends on a missing optional argument. This isn't too bad (the same thing happens if you access a missing optional argument). Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20323