From: Jerry D <jvdelisle2@gmail.com>
To: Tobias Burnus <tburnus@baylibre.com>, gfortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jerry D <jvdelisle2@gmail.com>
Subject: Re: [Patch] Fortran: List-directed read - accept again tab as alternative to space as separator [PR114304]
Date: Mon, 8 Apr 2024 11:21:28 -0700 [thread overview]
Message-ID: <704ed9f8-f7d4-4aaa-8ff6-fd9cc3abab06@gmail.com> (raw)
In-Reply-To: <529f47ca-c398-4e20-a0ef-507842f989d4@baylibre.com>
On 4/8/24 2:53 AM, Tobias Burnus wrote:
> Jerry D wrote:
>> See attached updated patch.
>
> It turned rather quickly out that this patch – committed as r14-9822-g93adf88cc6744a – caused regressions.
>
> Namely, real-world code use tab(s) as separator instead of spaces.
>
> [For instance, PR114304 which contains a named-list input file from SPEC CPU 2017; that example uses tabs before the '=' sign, but the issue is more generic.]
>
> I think the ISO Fortran standard only permits spaces, but as it feels natural and is widely supported, tabs are used and should remain supported.
>
> It is not quite clear how '\r' are or should be handled, but as eat_spaces did use it, I thought I would add one testcase using them as well.
>
> That test is not affected by my change; it did work before with GCC and still does – but it does fail with ifort/ifx/flang. I have not thought deeply whether it should be supported or not – and
> looking at the libgfortran source file, it often but (→ testcase) not consistently requires that an \n follows the \r.
>
> OK for mainline? [And: When the previous patch gets backported, this surely needs to be included as well.]
>
> Tobias
Good catch. I did not even think about tabs.
OK to commit and I will take care of it when I do the backport to 13.
Thanks!
Jerry
prev parent reply other threads:[~2024-04-08 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 1:33 [patch, libgfortran] PR114304 - [13/14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'" 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
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 ` Jerry D [this message]
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=704ed9f8-f7d4-4aaa-8ff6-fd9cc3abab06@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tburnus@baylibre.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).