public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95587] ICE in gfc_target_encode_expr, at fortran/target-memory.c:362 Date: Mon, 22 Jun 2020 19:27:39 +0000 [thread overview] Message-ID: <bug-95587-4-WYzKOs7gL9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95587-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95587 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:c00ca04ba7e46d2d59e5a4f95ee7121cdc4ba224 commit r10-8337-gc00ca04ba7e46d2d59e5a4f95ee7121cdc4ba224 Author: Harald Anlauf <anlauf@gmx.de> Date: Sat Jun 20 16:05:13 2020 +0200 PR fortran/95587 - ICE in gfc_target_encode_expr, at fortran/target-memory.c:362 EQUIVALENCE objects are subject to constraints listed in the Fortran 2018 standard, section 8.10.1.1. These constraints are to be checked also for CLASS variables. gcc/fortran/ PR fortran/95587 * match.c (gfc_match_equivalence): Check constraints on EQUIVALENCE objects also for CLASS variables. (cherry picked from commit 5eb947601bdce59f2ff26694327ad173c51c2724)
next prev parent reply other threads:[~2020-06-22 19:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 18:56 [Bug fortran/95587] New: " gscfq@t-online.de 2020-06-08 22:03 ` [Bug fortran/95587] " dominiq at lps dot ens.fr 2020-06-18 20:40 ` anlauf at gcc dot gnu.org 2020-06-18 21:28 ` anlauf at gcc dot gnu.org 2020-06-20 14:05 ` cvs-commit at gcc dot gnu.org 2020-06-22 19:27 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-23 20:18 ` cvs-commit at gcc dot gnu.org 2020-06-23 20:32 ` 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-95587-4-WYzKOs7gL9@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: linkBe 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).