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/100132] New: Optimization breaks pointer association Date: Sat, 17 Apr 2021 23:38:00 +0000 [thread overview] Message-ID: <bug-100132-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100132 Bug ID: 100132 Summary: Optimization breaks pointer association 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 50622 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50622&action=edit Fortran code showing problem Hi All! Pointer association is lost when compiling with -O1 or -O2, curiously not with -O3 unless -fcheck=recursion is used Seen on: GNU Fortran (GCC) 11.0.1 20210417 (experimental) GNU Fortran (GCC) 10.3.1 20210417 GNU Fortran (GCC) 9.3.1 20210417 Thank you very much. Best regards, José Rui
next reply other threads:[~2021-04-17 23:38 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-17 23:38 jrfsousa at gmail dot com [this message] 2021-04-18 0:20 ` [Bug fortran/100132] " jrfsousa at gmail dot com 2021-04-18 9:43 ` dominiq at lps dot ens.fr 2022-09-18 19:11 ` anlauf at gcc dot gnu.org 2022-09-19 20:21 ` anlauf at gcc dot gnu.org 2022-09-20 18:31 ` cvs-commit at gcc dot gnu.org 2022-10-01 18:17 ` cvs-commit at gcc dot gnu.org 2022-10-01 18:40 ` cvs-commit at gcc dot gnu.org 2022-10-01 18:55 ` cvs-commit at gcc dot gnu.org 2022-10-01 18:56 ` anlauf at gcc dot gnu.org 2022-10-17 20:36 ` 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-100132-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).