public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110629] Bug in assignment of derived type with deferred length character component Date: Tue, 11 Jul 2023 17:36:14 +0000 [thread overview] Message-ID: <bug-110629-4-YotVacJ0dh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110629-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110629 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org Priority|P3 |P4 --- Comment #1 from kargl at gcc dot gnu.org --- Thanks for the bug report. This seems to have been fixed in trunk. I don't have gfortran 13.1 installed so cannot test. % gfcx -o z a.f90 && ./z 1 |big | 2 |red | 3 |dog | % gfcx -o z -O a.f90 && ./z 1 |big | 2 |red | 3 |dog | % gfortran12 -o z -O a.f90 && ./z 1 |big | 2 ||big| 3 ||big|| There are a few Changelog entries over the last year that mention deferred length, but it's unclear which one might have fixed the issue.
next prev parent reply other threads:[~2023-07-11 17:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 14:02 [Bug fortran/110629] New: " townsend at astro dot wisc.edu 2023-07-11 17:36 ` kargl at gcc dot gnu.org [this message] 2023-07-11 17:47 ` [Bug fortran/110629] " anlauf at gcc dot gnu.org 2023-07-12 0:18 ` townsend at astro dot wisc.edu
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-110629-4-YotVacJ0dh@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).