public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107900] Select type with intrinsic type inside associate causes ICE / Segmenation fault Date: Fri, 16 Jun 2023 17:01:36 +0000 [thread overview] Message-ID: <bug-107900-4-PH9eYbwD2W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107900-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107900 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org --- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> --- Created attachment 55351 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55351&action=edit Fix for this PR Testcase: ! { dg-do run } ! ! Contributed by Karl Kaiser <kaiserkarl31@yahoo.com> ! program test class(*), pointer :: ptr1, ptr2(:) integer, target :: i = 42 integer :: check = 0 ! ptr1 => NULL() !This would fix the problem associate (c => ptr1) block select type (d => c) type is (integer) stop 1 class default check = 1 end select end block end associate ! Now do the same with the array version ! ptr2 => NULL() !This did not fix the problem associate (c => ptr2) block select type (d => c) type is (integer) stop 2 class default check = check + 10 end select end block end associate if (check .ne. 11) stop 3 end program test Regards Paul
next prev parent reply other threads:[~2023-06-16 17:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-28 20:43 [Bug fortran/107900] New: " kaiserkarl31 at yahoo dot com 2022-11-28 20:54 ` [Bug fortran/107900] " anlauf at gcc dot gnu.org 2023-06-16 17:01 ` pault at gcc dot gnu.org [this message] 2023-06-21 16:06 ` cvs-commit at gcc dot gnu.org 2023-06-21 21:05 ` pault 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-107900-4-PH9eYbwD2W@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).