public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98017] [8/9/10/11 Regression] Suspected regression (relative to 7.5) using PACK in iolist since r8-4151-g6c6bde30706c29ff Date: Fri, 11 Dec 2020 21:49:13 +0000 [thread overview] Message-ID: <bug-98017-4-Heo4oANSlf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98017-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98017 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #10 from anlauf at gcc dot gnu.org --- Fixed on master for gcc-11, and backported to 10-branch, as well as 9- and 8-branches with minor adjustment. Closing. Thanks for the report!
prev parent reply other threads:[~2020-12-11 21:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-26 12:58 [Bug fortran/98017] New: Suspected regression (relative to 7.5) using PACK in iolist layzarc at aol dot com 2020-11-26 14:13 ` [Bug fortran/98017] [8/9/10/11 Regression] Suspected regression (relative to 7.5) using PACK in iolist since r8-4151-g6c6bde30706c29ff marxin at gcc dot gnu.org 2020-11-27 20:22 ` anlauf at gcc dot gnu.org 2020-11-28 21:32 ` anlauf at gcc dot gnu.org 2020-11-28 22:02 ` anlauf at gcc dot gnu.org 2020-11-28 22:17 ` anlauf at gcc dot gnu.org 2020-11-29 22:25 ` cvs-commit at gcc dot gnu.org 2020-12-06 21:41 ` cvs-commit at gcc dot gnu.org 2020-12-11 21:28 ` cvs-commit at gcc dot gnu.org 2020-12-11 21:46 ` cvs-commit at gcc dot gnu.org 2020-12-11 21:49 ` anlauf at gcc dot gnu.org [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=bug-98017-4-Heo4oANSlf@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: linkBe 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).