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/87659] Memory corruption in array component of intent(in) unlimited polymorphic with optimization
Date: Mon, 17 Oct 2022 20:36:32 +0000 [thread overview]
Message-ID: <bug-87659-4-SpNevqUteM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87659-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87659
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
Status|WAITING |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #4)
> Adding several known-to-work/known-to-fail versions.
>
> Possibly fixed by one of Jose's patches that was recently committed and
> backported down to 10. (Could it be a dup of pr100132?)
Yep, reverting that patch re-introduces the bug. Marking as dup.
*** This bug has been marked as a duplicate of bug 100132 ***
prev parent reply other threads:[~2022-10-17 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-87659-4@http.gcc.gnu.org/bugzilla/>
2022-10-08 20:39 ` mikael at gcc dot gnu.org
2022-10-17 18:33 ` anlauf at gcc dot gnu.org
2022-10-17 20:36 ` 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-87659-4-SpNevqUteM@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).