public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arjen.markus895 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105054] New: Using one kind of pointer functions causes the compiler to hang Date: Fri, 25 Mar 2022 13:02:09 +0000 [thread overview] Message-ID: <bug-105054-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105054 Bug ID: 105054 Summary: Using one kind of pointer functions causes the compiler to hang Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: arjen.markus895 at gmail dot com Target Milestone: --- Created attachment 52686 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52686&action=edit Program that demonstrates the bug The attached program causes the gfortran, version 11.2.0, to hang whereas version 10.2.0 produces a program that works correctly. (Note: Intel Fortran oneAPI produces strange error messsages)
next reply other threads:[~2022-03-25 13:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-25 13:02 arjen.markus895 at gmail dot com [this message] 2022-03-25 13:45 ` [Bug fortran/105054] " mscfd at gmx dot net 2022-03-25 14:26 ` [Bug fortran/105054] [11/12 Regression] Using one kind of pointer functions causes the compiler to hang since r11-3029-g2b0df0a6ac79b34f marxin at gcc dot gnu.org 2022-04-04 11:32 ` rguenth at gcc dot gnu.org 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2023-05-29 10:06 ` [Bug fortran/105054] [11/12/13/14 " jakub 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-105054-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).