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/115070] [13/14/15 Regression] ICE using IEEE_ARITHMETIC in a derived type method with class, intent(out) Date: Tue, 21 May 2024 12:03:58 +0000 [thread overview] Message-ID: <bug-115070-4-RoMzJ2PkO9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115070-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115070 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 #9 from Paul Thomas <pault at gcc dot gnu.org> --- Created attachment 58263 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58263&action=edit Patch that fixes this PR Somehow, when a null is returned from the call to gfc_trans_class_init_assign, the messing around with blocks at the end of gfc_generate_function_code loses the declaration. I tried giving the ieee calls their own block and merging it to the top of 'body'. That fixed this PR but broke a number of ieee tests in the testsuite. This fix is not very elegant but it does work and even regtests OK. I am continuing to work on it before submitting this patch. Paul
prev parent reply other threads:[~2024-05-21 12:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-13 14:23 [Bug fortran/115070] New: ICE using IEEE_ARITHMETIC in a derived type method with intent(out) statement bardeau at iram dot fr 2024-05-13 17:09 ` [Bug fortran/115070] [13/14/15 Regression] ICE using IEEE_ARITHMETIC in a derived type method with class, intent(out) anlauf at gcc dot gnu.org 2024-05-13 17:24 ` anlauf at gcc dot gnu.org 2024-05-15 6:31 ` pault at gcc dot gnu.org 2024-05-16 10:00 ` bardeau at iram dot fr 2024-05-16 10:17 ` fxcoudert at gcc dot gnu.org 2024-05-16 10:59 ` fxcoudert at gcc dot gnu.org 2024-05-17 14:32 ` pault at gcc dot gnu.org 2024-05-21 9:20 ` jakub at gcc dot gnu.org 2024-05-21 12:03 ` pault 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-115070-4-RoMzJ2PkO9@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).