From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by sourceware.org (Postfix) with ESMTPS id 3FC273858C52; Thu, 29 Feb 2024 18:13:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3FC273858C52 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=troutmask.apl.washington.edu Authentication-Results: sourceware.org; spf=none smtp.mailfrom=troutmask.apl.washington.edu ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 3FC273858C52 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=128.95.76.21 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709230421; cv=none; b=H8GfPP5tz1KbnSMQovIdGF/xUxaKzSwTN5zxytVciSh0Yd/eoG7mYv3entShIpNiTq8et8UtXLqeeI5Z0VAW0zmMqPFS6SmG9lvywMkjpwJMzebWgO6FaIvpJOnrXtDmpHPHMUWlMwA3CJVLfMbGMBnyxtE8HuJgFGlB8AJrAjc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709230421; c=relaxed/simple; bh=xwoSzxVit6YIjz4mL0pHho8ZSTQ8p0R4/pq8WOaO8aY=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=YhN5K8/853VBWBtCmt9jFiqXm7Te/8IfyT2L0UOwqc9CttomO5WMK9w1nr3T9wBZR6Ye8FgB4u/ldNyEgg9GJkRkXRmyrbzCFbiPcItfS37lWXDM9E9BLJJq6C2n8nCYo9vAG83318+J1MBPgZmJWqC+ubUIKFUP6rQDSCYVA/E= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.17.1/8.17.1) with ESMTP id 41TIDdRu024219; Thu, 29 Feb 2024 10:13:39 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) DKIM-Filter: OpenDKIM Filter v2.10.3 troutmask.apl.washington.edu 41TIDdRu024219 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=troutmask.apl.washington.edu; s=troutmask; t=1709230419; bh=xwoSzxVit6YIjz4mL0pHho8ZSTQ8p0R4/pq8WOaO8aY=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=X49vaxRJEIjXLyZn/Gg+pGzHKBUmJlSla5mNTlPbLusBeHIKCbPGIU83cPdNNaWur UrvgvVso+mq8BoRaEPJ8d4i2l0KTFvQgmUTiEhp5P66aGj4zCv1sTM8K1qczEMyi4u 8mJlTIBSq2EgsaV86M/IhG8irIEpApMGOYsNNvht0LECDqv2Cq/NIJI1ZnFpkzuEbF 6M+0Dxev6IyW2Ub4zg5kqx+FKjg+xkRqC2KiIffaUKFNooETRLReZkecuAHLsP+Z/7 cqCeolzqL0I5YMZGOXUaKfFDJS2Lz528KaT/eqOvGKULKGeD2NzrgiLAHNMO4Ck3Lk d/6tHM/9PL0JQ== Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.17.1/8.17.1/Submit) id 41TIDcEj024218; Thu, 29 Feb 2024 10:13:38 -0800 (PST) (envelope-from sgk) Date: Thu, 29 Feb 2024 10:13:38 -0800 From: Steve Kargl To: Jerry D Cc: Bernhard Reutner-Fischer , gfortran , gcc-patches Subject: Re: [patch, libgfortran] Part 2: PR105456 Child I/O does not propage iostat Message-ID: Reply-To: sgk@troutmask.apl.washington.edu References: <943c3685-c4d4-4f22-8b65-6336f8770043@gmail.com> <20240229104705.62e46010@nbbrfq.loc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,DKIM_INVALID,DKIM_SIGNED,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, Feb 29, 2024 at 09:36:43AM -0800, Jerry D wrote: > On 2/29/24 1:47 AM, Bernhard Reutner-Fischer wrote: > > > And, just for my own education, the length limitation of iomsg to 255 > > chars is not backed by the standard AFAICS, right? It's just our > > STRERR_MAXSZ? > > Yes, its what we have had for a long lone time. Once you throw an error > things get very processor dependent. I found MSGLEN set to 100 and IOMSG_len > to 256. Nothing magic about it. > There is no restriction on the length for the iomsg-variable that receives the generated error message. In fact, if the iomsg-variable has a deferred-length type parameter, then (re)-allocation to the exact length is expected. F2023 12.11.6 IOMSG= specifier If an error, end-of-file, or end-of-record condition occurs during execution of an input/output statement, iomsg-variable is assigned an explanatory message, as if by intrinsic assignment. If no such condition occurs, the definition status and value of iomsg-variable are unchanged. character(len=23) emsg read(fd,*,iomsg=emsg) Here, the generated iomsg is either truncated to a length of 23 or padded with blanks to a length of 23. character(len=:), allocatable :: emsg read(fd,*,iomsg=emsg) Here, emsg should have the length of whatever error message was generated. HTH -- Steve