From: Tobias Burnus <tburnus@baylibre.com>
To: Jerry D <jvdelisle2@gmail.com>, gfortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, libgfortran] PR114304 - [13/14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'"
Date: Sat, 6 Apr 2024 07:17:37 +0200 [thread overview]
Message-ID: <fe17957f-d5c7-4398-8f9b-a3462f29b29a@baylibre.com> (raw)
In-Reply-To: <cbb83676-81c5-4a1d-addd-9c7b0f4b1e64@gmail.com>
Hi Jerry, hello world,
Jerry D wrote:
> On 4/5/24 10:47 AM, Jerry D wrote:
>> On 4/4/24 2:41 PM, Tobias Burnus wrote:
>>> I think for the current testcases, I like the patch – the question
>>> is only what's about:
>>> ',3' as input for 'comma' (or '.3' as input for 'point')
>>> [...]
>>> But for 'comma': [...]
>>> * GCC with your patch: Same result: ios != 0 and nothing read.
>>>
>>> Expected: [...] read-in value is 0.3. [...]
> See attached updated patch.
> Regressions tested on x86-64. OK for trunk and 13 after a bit.
OK. Thanks for the patch!
Tobias
next prev parent reply other threads:[~2024-04-06 5:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 1:33 Jerry D
2024-04-04 8:17 ` Paul Richard Thomas
2024-04-04 9:31 ` Tobias Burnus
2024-04-04 20:05 ` Jerry D
2024-04-04 21:04 ` Jerry D
2024-04-04 21:41 ` Tobias Burnus
2024-04-05 17:47 ` Jerry D
2024-04-06 2:38 ` Jerry D
2024-04-06 5:17 ` Tobias Burnus [this message]
2024-04-08 9:53 ` [Patch] Fortran: List-directed read - accept again tab as alternative to space as separator [PR114304] (was: [patch, libgfortran] PR114304 - [13/14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'") Tobias Burnus
2024-04-08 18:21 ` [Patch] Fortran: List-directed read - accept again tab as alternative to space as separator [PR114304] 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=fe17957f-d5c7-4398-8f9b-a3462f29b29a@baylibre.com \
--to=tburnus@baylibre.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle2@gmail.com \
/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).