public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jrfsousa at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95138] New: ICE on transfer to unlimited polymorphic Date: Thu, 14 May 2020 18:09:29 +0000 [thread overview] Message-ID: <bug-95138-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95138 Bug ID: 95138 Summary: ICE on transfer to unlimited polymorphic Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jrfsousa at gmail dot com Target Milestone: --- Created attachment 48536 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48536&action=edit Fortran code demonstrating problems. Hi all! ICE on 10 and 11, 9 compiles part of the code, so there is also some aspect of regression here. Using -Wsurprising gives surprising (to me...) diagnostics. Not sure if all the code is kosher, most likely it is not... using: GNU Fortran (GCC) 11.0.0 20200513 (experimental) GNU Fortran (GCC) 10.1.1 20200513 GNU Fortran (GCC) 9.3.1 20200513 Thank you very much. Best regards, José Rui
next reply other threads:[~2020-05-14 18:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-14 18:09 jrfsousa at gmail dot com [this message] 2020-05-14 21:00 ` [Bug fortran/95138] " anlauf at gcc dot gnu.org 2020-05-16 12:54 ` anlauf at gcc dot gnu.org 2020-06-09 14:21 ` dominiq at lps dot ens.fr
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-95138-4@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).