public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/113363] ICE on ASSOCIATE and unlimited polymorphic function
Date: Sun, 14 Jan 2024 09:22:38 +0000 [thread overview]
Message-ID: <bug-113363-4-KW7mi8URy7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113363-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113363
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-01-14
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
>
> Both allocation with source and assignment are broken :-(
With numerical output from foo ([1,2,3,4,5]), we get:
1 3 5 33 1
1 2 3 4 5
1 2 3 4 5
So allocation with source is broken here as well but assignment is OK.
next prev parent reply other threads:[~2024-01-14 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 20:31 [Bug fortran/113363] New: " anlauf at gcc dot gnu.org
2024-01-14 8:54 ` [Bug fortran/113363] " pault at gcc dot gnu.org
2024-01-14 9:22 ` pault at gcc dot gnu.org [this message]
2024-01-17 14:46 ` pault at gcc dot gnu.org
2024-04-03 18:56 ` anlauf at gcc dot gnu.org
2024-04-04 6:27 ` pault at gcc dot gnu.org
2024-04-04 19:12 ` anlauf at gcc dot gnu.org
2024-04-06 10:05 ` pault at gcc dot gnu.org
2024-05-07 7:43 ` rguenth at gcc dot gnu.org
2024-05-13 6:27 ` cvs-commit at gcc dot gnu.org
2024-05-13 6:37 ` pault 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-113363-4-KW7mi8URy7@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).