public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108450] [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 since r12-5793-g689407ef916503b2 Date: Fri, 20 Jan 2023 18:03:53 +0000 [thread overview] Message-ID: <bug-108450-4-qHX9dhLdCJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108450 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- Interestingly, it is resolved twice. First for: (gdb) p gfc_debug_expr(e) maxloc[((p:a) (mask = p:l))] via resolve_all_program_units → gfc_resolve → gfc_resolve → resolve_codes → gfc_resolve_code → gfc_resolve_blocks → gfc_resolve_code → gfc_resolve_expr And then via: ... → resolve_omp_atomic → gfc_resolve_expr The problem is that in the latter case, the 'e' is now: maxloc[((p:a(FULL)) (mask = p:l) (.false.))] and the unprefixed .false. seems to cause the problems. The intrinsic uses: RESULT = MAXLOC(ARRAY, DIM [, MASK] [,KIND] [,BACK]) RESULT = MAXLOC(ARRAY [, MASK] [,KIND] [,BACK]) During the first call to check_specific, maxloc[((p:a(FULL)) (mask = p:l))] is turned into maxloc[((p:a(FULL)) ((arg not-present)) (mask = p:l) ((arg not-present)) ((arg not-present)))] via 4774 if (!sort_actual (specific->name, ap, specific->formal, &expr->where)) The null-args are later removed via 'remove_nullargs (ap);' * * * Thus, it looks as if resolving the RHS expression twice is wrong.
next prev parent reply other threads:[~2023-01-20 18:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 18:23 [Bug fortran/108450] New: [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 gscfq@t-online.de 2023-01-19 7:47 ` [Bug fortran/108450] " rguenth at gcc dot gnu.org 2023-01-19 14:16 ` [Bug fortran/108450] [12/13 Regression] ICE in sort_actual, at fortran/intrinsic.cc:4380 since r12-5793-g689407ef916503b2 marxin at gcc dot gnu.org 2023-01-20 18:03 ` burnus at gcc dot gnu.org [this message] 2023-01-29 19:47 ` mikael at gcc dot gnu.org 2023-01-29 20:57 ` cvs-commit at gcc dot gnu.org 2023-02-05 21:53 ` cvs-commit at gcc dot gnu.org 2023-02-05 22:22 ` mikael 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-108450-4-qHX9dhLdCJ@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).