From: rep.dot.nop@gmail.com
To: Jerry D <jvdelisle2@gmail.com>, sgk@troutmask.apl.washington.edu
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: [patch, libgfortran] Part 2: PR105456 Child I/O does not propage iostat
Date: Fri, 01 Mar 2024 21:50:08 +0100 [thread overview]
Message-ID: <13A72F77-9F32-4C9A-B798-E81EFF576058@gmail.com> (raw)
In-Reply-To: <5e5653eb-aeea-4eec-be52-a5adea71b201@gmail.com>
On 29 February 2024 23:28:44 CET, Jerry D <jvdelisle2@gmail.com> wrote:
>On 2/29/24 12:56 PM, Steve Kargl wrote:
>> On Thu, Feb 29, 2024 at 10:28:19AM -0800, Jerry D wrote:
>>> On 2/29/24 10:13 AM, Steve Kargl wrote:
>>>> 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.
It was system dependent.
In the lib, here, it was probed at runtime, cross used IOV_MAX on lunix per default, in the non error case looped.
>PS I wish my mail client would not wrap text on me, working on that issue.
try :paste
Or set tw=0, although 80 makes sense for me, or 72 in mail (if you are able to clip)
next prev parent reply other threads:[~2024-03-01 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 5:29 Jerry D
2024-02-29 9:47 ` Bernhard Reutner-Fischer
2024-02-29 17:36 ` Jerry D
2024-02-29 18:13 ` Steve Kargl
2024-02-29 18:28 ` Jerry D
2024-02-29 20:56 ` Steve Kargl
2024-02-29 22:28 ` Jerry D
2024-03-01 20:50 ` rep.dot.nop [this message]
[not found] ` <05A1AEE6-6A68-4D4F-8BEA-6E87969E19E7@gmail.com>
2024-03-05 3:15 ` Jerry D
2024-03-05 21:30 ` rep.dot.nop
2024-03-05 21:37 ` Harald Anlauf
2024-03-05 21:51 ` Harald Anlauf
2024-03-06 4:06 ` Jerry D
2024-03-06 6:06 ` Steve Kargl
2024-03-06 17:13 ` Harald Anlauf
2024-03-06 17:13 ` Harald Anlauf
2024-03-06 18:03 ` Jerry D
2024-03-06 18:24 ` Jerry D
2024-03-07 4:01 ` Jerry D
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13A72F77-9F32-4C9A-B798-E81EFF576058@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle2@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).