public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102900] ICE via gfc_class_data_get with alloc_comp_class_4.f03 or proc_ptr_52.f90 using -fcheck=all Date: Sat, 24 Sep 2022 19:45:20 +0000 [thread overview] Message-ID: <bug-102900-4-hE5gq7DOEJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102900-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102900 --- Comment #6 from anlauf at gcc dot gnu.org --- (In reply to anlauf from comment #5) > (In reply to anlauf from comment #4) > > The ICE is resolved by Jose's patch to PR100136, which was just accepted. Update: with current mainline (PR100136 now fixed), the runtime failure of alloc_comp_class_4.f03 with -fcheck=all is due to a missing allocate in function c_init2. Adding allocate (c_init2) resolves this. This testcase is thus incompatible with -fcheck=pointer. > ... but not for proc_ptr_52.f90 with -fcheck=pointer This one remains.
prev parent reply other threads:[~2022-09-24 19:45 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-22 16:06 [Bug fortran/102900] New: ICE via gfc_class_data_get in alloc_comp_class_4.f03 with -fcheck=all burnus at gcc dot gnu.org 2021-10-22 17:52 ` [Bug fortran/102900] ICE via gfc_class_data_get with alloc_comp_class_4.f03 or proc_ptr_52.f90 using -fcheck=all burnus at gcc dot gnu.org 2021-10-23 17:26 ` dominiq at lps dot ens.fr 2021-10-25 9:04 ` marxin at gcc dot gnu.org 2021-10-25 9:56 ` anlauf at gcc dot gnu.org 2021-10-25 21:05 ` anlauf at gcc dot gnu.org 2022-09-24 19:45 ` anlauf at gcc dot gnu.org [this message]
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-102900-4-hE5gq7DOEJ@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).