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 fortran/109358] Wrong formatting with T-descriptor during stream output
Date: Tue, 13 Feb 2024 03:26:31 +0000	[thread overview]
Message-ID: <bug-109358-4-Ezk2fupQfA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109358-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r13-8322-gd85a658402d5433ff223ce8f4e70174ed8a20428
Author: Jerry DeLisle <jvdelisle@gcc.gnu.org>
Date:   Mon Feb 12 13:12:08 2024 -0800

    libgfortran: Adjust bytes_left and pos for access="STREAM".

    During tab edits, the pos (position) and bytes_used
    Variables were not being set correctly for stream I/O.
    Since stream I/O does not have 'real' records, the
    format buffer active length must be used instead of
    the record length variable.

           PR libgfortran/109358

    libgfortran/ChangeLog:

            * io/transfer.c (formatted_transfer_scalar_write): Adjust
            bytes_used and pos variable for stream access.

    gcc/testsuite/ChangeLog:

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

    (cherry picked from commit 153ce7a78edbe339fa0b1cd314dea0554f59faf0)

  parent reply	other threads:[~2024-02-13  3:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 10:49 [Bug fortran/109358] New: " baradi09 at gmail dot com
2023-03-31 20:27 ` [Bug fortran/109358] " jvdelisle at gcc dot gnu.org
2023-04-06  2:48 ` jvdelisle at gcc dot gnu.org
2023-04-06  3:56 ` kargl at gcc dot gnu.org
2023-04-15  3:31 ` jvdelisle at gcc dot gnu.org
2023-04-16  8:18 ` baradi09 at gmail dot com
2023-06-02  1:51 ` jvdelisle at gcc dot gnu.org
2023-06-02  5:17 ` sgk at troutmask dot apl.washington.edu
2024-02-03 18:28 ` jvdelisle at gcc dot gnu.org
2024-02-08 18:14 ` jvdelisle at gcc dot gnu.org
2024-02-08 18:17 ` jvdelisle at gcc dot gnu.org
2024-02-12 20:05 ` jvdelisle at gcc dot gnu.org
2024-02-12 23:30 ` cvs-commit at gcc dot gnu.org
2024-02-13  3:26 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-14 19:58 ` jvdelisle at gcc dot gnu.org
2024-02-17 20:16 ` anlauf at gcc dot gnu.org
2024-02-19  2:38 ` 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-109358-4-Ezk2fupQfA@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).