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/70231] Runtime error: Different CHARACTER lengths in array constructor with allocatable array and -O0
Date: Mon, 18 Sep 2023 19:23:48 +0000 [thread overview]
Message-ID: <bug-70231-4-qal4m7F0hc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-70231-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70231
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #3 from anlauf at gcc dot gnu.org ---
Created attachment 55925
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55925&action=edit
Patch
The issue here is that the "bounds check" does not properly initialize the
string length temporary that is used for checking. The attached patch
uses what we have after calling get_array_ctor_strlen.
next parent reply other threads:[~2023-09-18 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-70231-4@http.gcc.gnu.org/bugzilla/>
2023-09-18 19:23 ` anlauf at gcc dot gnu.org [this message]
2023-09-18 20:27 ` anlauf at gcc dot gnu.org
2023-09-19 17:15 ` cvs-commit at gcc dot gnu.org
2023-09-19 19:16 ` anlauf 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-70231-4-qal4m7F0hc@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).