public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/99210] X editing for reading file with encoding='utf-8'
Date: Wed, 14 Feb 2024 15:58:42 +0000	[thread overview]
Message-ID: <bug-99210-4-iJaCywFgpE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99210-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jerry DeLisle <jvdelisle@gcc.gnu.org>:

https://gcc.gnu.org/g:b79d3e6a9284703b70688122f7d4955e7c50804a

commit r14-8983-gb79d3e6a9284703b70688122f7d4955e7c50804a
Author: Jerry DeLisle <jvdelisle@gcc.gnu.org>
Date:   Tue Feb 13 14:32:21 2024 -0800

    Fortran: Implement read_x for UTF-8 encoded files.

            PR fortran/99210

    libgfortran/ChangeLog:

            * io/read.c (read_x): If UTF-8 encoding is enabled, use
            read_utf8 to move one character over in the read buffer.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/pr99210.f90: New test.

  parent reply	other threads:[~2024-02-14 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 22:40 [Bug libfortran/99210] New: " leo at sai dot msu.ru
2021-02-22 22:44 ` [Bug libfortran/99210] " leo at sai dot msu.ru
2021-02-23  1:34 ` jvdelisle at gcc dot gnu.org
2021-02-28  3:25 ` jvdelisle at gcc dot gnu.org
2021-04-17  3:26 ` jvdelisle at gcc dot gnu.org
2021-05-04  2:29 ` jvdelisle at gcc dot gnu.org
2024-02-13  5:00 ` jvdelisle at gcc dot gnu.org
2024-02-13 20:07 ` jvdelisle at gcc dot gnu.org
2024-02-13 22:56 ` jvdelisle at gcc dot gnu.org
2024-02-14 15:58 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-14 20:00 ` jvdelisle at gcc dot gnu.org

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=bug-99210-4-iJaCywFgpE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).