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/58331] [OOP] Bogus rank checking with explicit-/assumed-size arrays and CLASS Date: Sat, 22 Mar 2014 15:02:00 -0000 [thread overview] Message-ID: <bug-58331-4-bmFt1UBZ02@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58331-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58331 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2014-03-22 Ever confirmed|0 |1 --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- With the patch in comment 2, I also get (r208765) pr58331.f90: In function 'upv': pr58331.f90:19:0: error: non-trivial conversion at assignment program upv ^ struct array1_unknown struct array2_integer(kind=4) class.6._data = parm.7; pr58331.f90:19:0: internal compiler error: verify_gimple failed I also get the same ICE if I use class(*), intent(in) :: a(..) ... print *, rank(a)
next prev parent reply other threads:[~2014-03-22 15:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-06 6:00 [Bug fortran/58331] New: " burnus at gcc dot gnu.org 2013-09-06 21:35 ` [Bug fortran/58331] " burnus at gcc dot gnu.org 2013-09-08 16:46 ` burnus at gcc dot gnu.org 2014-03-22 15:02 ` dominiq at lps dot ens.fr [this message] 2023-03-06 21:43 ` anlauf at gcc dot gnu.org 2023-03-06 22:13 ` anlauf at gcc dot gnu.org 2023-03-07 9:14 ` burnus at gcc dot gnu.org 2023-03-09 19:44 ` anlauf at gcc dot gnu.org 2023-03-14 19:39 ` anlauf at gcc dot gnu.org 2023-03-15 8:58 ` burnus at gcc dot gnu.org 2023-03-15 19:22 ` cvs-commit at gcc dot gnu.org 2023-03-15 20:03 ` 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-58331-4-bmFt1UBZ02@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).