public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103366] [9/10/11/12 Regression] ICE in gfc_conv_gfc_desc_to_cfi_desc, at fortran/trans-expr.c:5647 Date: Mon, 03 Jan 2022 11:55:43 +0000 [thread overview] Message-ID: <bug-103366-4-1lJZtJbOm0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103366-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103366 --- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> --- (In reply to Paul Thomas from comment #4) > (In reply to Martin Liška from comment #3) > > (In reply to Andrew Pinski from comment #2) > > > (In reply to Martin Liška from comment #1) > > > > Started with r9-5372-gbbf18dc5d248a79a. > > > > > > Are you sure? > > > > Yes, I am. > > > > > Because the reporter said this: > > > > This changed between 20211017 and 20211024 : > > > > It's true with disabled checking. > > ifort 2021.1 Beta 20201112 gives: > ../pr103366/pr103366.f90(8): error #8769: If the actual argument is > unlimited polymorphic, the corresponding dummy argument must also be > unlimited polymorphic. [X] > call s(x) > -------------^ > ../pr103366/pr103366.f90(8): error #8788: This assumed-size or > nonallocatable nonpointer assumed-rank array is an actual argument > corresponding to an INTENT(OUT) assumed-rank array dummy so it cannot be > polymorphic, finalizable, have an allocatable ultimate component, or have > default initialization. [X] > call s(x) > -------------^ > compilation aborted for ../pr103366/pr103366.f90 (code 1) > > Paul >From F2017: 15.5.2.5 The actual argument shall be polymorphic if and only if the associated dummy argument is polymorphic, and either both the actual and dummy arguments shall be unlimited polymorphic, or the declared type of the actual argument shall be the same as the declared type of the dummy argument. As yet, I have not found the constraints leading to the second error. Cheers Paul
next prev parent reply other threads:[~2022-01-03 11:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 19:38 [Bug fortran/103366] New: [12 " gscfq@t-online.de 2021-11-23 7:33 ` [Bug fortran/103366] " rguenth at gcc dot gnu.org 2021-11-23 7:56 ` marxin at gcc dot gnu.org 2021-11-23 8:01 ` pinskia at gcc dot gnu.org 2021-11-23 8:10 ` marxin at gcc dot gnu.org 2021-11-23 8:12 ` [Bug fortran/103366] [9/10/11/12 " pinskia at gcc dot gnu.org 2022-01-03 9:15 ` pault at gcc dot gnu.org 2022-01-03 11:55 ` pault at gcc dot gnu.org [this message] 2022-01-03 12:33 ` pault at gcc dot gnu.org 2022-01-06 1:07 ` sandra at gcc dot gnu.org 2022-01-10 16:55 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:46 ` [Bug fortran/103366] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:47 ` jakub at gcc dot gnu.org 2022-07-13 19:16 ` anlauf at gcc dot gnu.org 2023-04-19 9:19 ` [Bug fortran/103366] [10/11/12/13/14 " pault 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-103366-4-1lJZtJbOm0@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).