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/107819] ICE in gfc_check_argument_var_dependency, at fortran/dependency.cc:978 Date: Tue, 22 Nov 2022 19:41:54 +0000 [thread overview] Message-ID: <bug-107819-4-2fQEoBW9EO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107819 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-11-22 Keywords| |ice-on-invalid-code, | |ice-on-valid-code Ever confirmed|0 |1 CC| |anlauf at gcc dot gnu.org --- Comment #2 from anlauf at gcc dot gnu.org --- Confirmed. Potential patch: diff --git a/gcc/fortran/trans-stmt.cc b/gcc/fortran/trans-stmt.cc index fd6d294147e..b288f1f9050 100644 --- a/gcc/fortran/trans-stmt.cc +++ b/gcc/fortran/trans-stmt.cc @@ -264,6 +264,7 @@ gfc_conv_elemental_dependencies (gfc_se * se, gfc_se * loopse, if (e->expr_type == EXPR_VARIABLE && e->rank && fsym && fsym->attr.intent != INTENT_IN + && !fsym->attr.value && gfc_check_fncall_dependency (e, fsym->attr.intent, sym, arg0, check_variable)) { Note that we get a (correct) warning for z1 after this fix: pr107819-z1.f90:4:10-16: 4 | call s (a(n), a) | 2 1 Warning: INTENT(OUT) actual argument at (1) might interfere with actual argument at (2).
next prev parent reply other threads:[~2022-11-22 19:42 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-22 17:41 [Bug fortran/107819] New: " gscfq@t-online.de 2022-11-22 17:42 ` [Bug fortran/107819] " gscfq@t-online.de 2022-11-22 19:41 ` anlauf at gcc dot gnu.org [this message] 2022-11-22 21:01 ` anlauf at gcc dot gnu.org 2022-11-24 13:12 ` mikael at gcc dot gnu.org 2022-11-24 17:07 ` anlauf at gcc dot gnu.org 2022-11-24 19:07 ` mikael at gcc dot gnu.org 2022-11-24 21:24 ` anlauf at gcc dot gnu.org 2022-11-24 21:40 ` mikael at gcc dot gnu.org 2022-11-24 22:02 ` mikael at gcc dot gnu.org 2022-11-25 22:06 ` anlauf at gcc dot gnu.org 2022-11-26 20:56 ` anlauf at gcc dot gnu.org 2022-11-26 21:05 ` mikael at gcc dot gnu.org 2022-11-27 20:33 ` anlauf at gcc dot gnu.org 2022-11-28 18:54 ` cvs-commit at gcc dot gnu.org 2022-11-28 21:27 ` anlauf at gcc dot gnu.org 2022-11-28 21:57 ` pinskia 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-107819-4-2fQEoBW9EO@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).