public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95718] [8/9/10/11 Regression] Wrong pointer associated status without initialization
Date: Wed, 17 Jun 2020 10:12:49 +0000 [thread overview]
Message-ID: <bug-95718-4-CqVaB1S5Lu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95718-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95718
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |10.1.0, 11.0, 6.5.0, 7.4.0,
| |8.3.0, 9.2.0
Priority|P3 |P4
Ever confirmed|0 |1
Keywords| |wrong-code
Target Milestone|--- |8.4
Last reconfirmed| |2020-06-17
Status|UNCONFIRMED |NEW
Summary|Wrong pointer associated |[8/9/10/11 Regression]
|status without |Wrong pointer associated
|initialization |status without
| |initialization
Known to work| |5.5.0
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
GCC5.5.0 gives
F associated(ptr)
F associated(ptr1)
F associated(ptr2)
F associated(ptr3)
F associated(ptr4)
next prev parent reply other threads:[~2020-06-17 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 9:04 [Bug fortran/95718] New: " peng.wang@compiler-dev.com
2020-06-17 10:12 ` dominiq at lps dot ens.fr [this message]
2020-06-17 10:44 ` [Bug fortran/95718] [8/9/10/11 Regression] " dominiq at lps dot ens.fr
2020-06-17 15:52 ` kargl at gcc dot gnu.org
2020-07-23 7:29 ` peng.wang@compiler-dev.com
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-95718-4-CqVaB1S5Lu@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).