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/100136] New: ICE, regression, using flag -fcheck=pointer Date: Sun, 18 Apr 2021 15:04:21 +0000 [thread overview] Message-ID: <bug-100136-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100136 Bug ID: 100136 Summary: ICE, regression, using flag -fcheck=pointer 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 50623 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50623&action=edit Fortran code showing problem Hi All! ICE using flag -fcheck=pointer. Seen on: GNU Fortran (GCC) 11.0.1 20210417 (experimental) Older versions don't ICE, but don't do any checking either... Thank you very much. Best regards, José Rui
next reply other threads:[~2021-04-18 15:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-18 15:04 jrfsousa at gmail dot com [this message] 2021-04-19 7:23 ` [Bug fortran/100136] [11 Regression] " marxin at gcc dot gnu.org 2021-04-19 18:37 ` anlauf at gcc dot gnu.org 2021-04-21 10:27 ` [Bug fortran/100136] [11/12 " jrfsousa at gmail dot com 2021-07-06 6:44 ` rguenth at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2022-08-27 20:06 ` [Bug fortran/100136] [11/12/13 " anlauf at gcc dot gnu.org 2022-09-04 20:57 ` cvs-commit at gcc dot gnu.org 2022-09-05 19:25 ` cvs-commit at gcc dot gnu.org 2022-09-05 19:34 ` cvs-commit at gcc dot gnu.org 2022-09-05 19:35 ` 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-100136-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).