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/97592] [10/11/12/13 Regression] Incorrectly set pointer remapping with array pointer argument to CONTIGUOUS dummy
Date: Tue, 21 Mar 2023 19:44:54 +0000 [thread overview]
Message-ID: <bug-97592-4-hXVqnp4LQJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97592-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97592
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |7.5.0, 8.5.0
Keywords| |wrong-code
Summary|Incorrectly set pointer |[10/11/12/13 Regression]
|remapping with array |Incorrectly set pointer
|pointer argument to |remapping with array
|CONTIGUOUS dummy |pointer argument to
| |CONTIGUOUS dummy
Target Milestone|--- |10.5
Known to fail| |10.4.0, 11.3.0, 12.2.0,
| |13.0, 9.5.0
--- Comment #4 from anlauf at gcc dot gnu.org ---
Adding known-to-work, known-to-fail versions.
next prev parent reply other threads:[~2023-03-21 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 14:25 [Bug fortran/97592] New: " reubendb at gmail dot com
2020-10-27 19:07 ` [Bug fortran/97592] " anlauf at gcc dot gnu.org
2021-02-14 18:17 ` dominiq at lps dot ens.fr
2022-03-14 21:39 ` anlauf at gcc dot gnu.org
2023-03-21 19:44 ` anlauf at gcc dot gnu.org [this message]
2023-03-21 19:57 ` [Bug fortran/97592] [10/11/12/13 Regression] " anlauf at gcc dot gnu.org
2023-07-07 10:38 ` [Bug fortran/97592] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-12-15 22:31 ` anlauf at gcc dot gnu.org
2023-12-16 18:29 ` anlauf at gcc dot gnu.org
2023-12-17 17:33 ` cvs-commit at gcc dot gnu.org
2023-12-27 19:27 ` cvs-commit at gcc dot gnu.org
2023-12-27 19:33 ` 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-97592-4-hXVqnp4LQJ@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).