public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99585] ICE with SIZE intrinsic on nested derived type components Date: Sat, 19 Mar 2022 07:49:36 +0000 [thread overview] Message-ID: <bug-99585-4-NehsMjvEDp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99585-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99585 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:d32402e6167294ad8ba84ffccebff1b098d2b4e1 commit r11-9671-gd32402e6167294ad8ba84ffccebff1b098d2b4e1 Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Mar 7 22:11:33 2022 +0100 Fortran: Fix gfc_maybe_dereference_var [PR104430][PR99585] PR fortran/99585 PR fortran/104430 gcc/fortran/ChangeLog: * trans-expr.c (conv_parent_component_references): Fix comment; simplify comparison. (gfc_maybe_dereference_var): Avoid d referencing a nonpointer. gcc/testsuite/ChangeLog: * gfortran.dg/class_result_10.f90: New test. (cherry picked from commit c0134b7383992aab5c1a91440dbdd8fbb747169c)
next prev parent reply other threads:[~2022-03-19 7:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-14 19:45 [Bug fortran/99585] New: " anlauf at gcc dot gnu.org 2021-03-14 19:46 ` [Bug fortran/99585] " anlauf at gcc dot gnu.org 2021-03-14 20:27 ` anlauf at gcc dot gnu.org 2021-03-14 21:06 ` anlauf at gcc dot gnu.org 2021-03-15 9:07 ` marxin at gcc dot gnu.org 2022-03-07 21:12 ` cvs-commit at gcc dot gnu.org 2022-03-19 7:49 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-27 19:48 ` 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-99585-4-NehsMjvEDp@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).