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/96312] [10/11 Regression] Reallocation on assignment uses undefined variables Date: Mon, 10 Aug 2020 05:22:34 +0000 [thread overview] Message-ID: <bug-96312-4-rSDab0Ood2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96312-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96312 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>: https://gcc.gnu.org/g:abb276d0eca218e62e5ed50babf12ff544250759 commit r11-2625-gabb276d0eca218e62e5ed50babf12ff544250759 Author: Paul Thomas <pault@gcc.gnu.org> Date: Mon Aug 10 06:22:22 2020 +0100 This patch fixes PR96312. Cures a used uninitialized warning. 2020-08-10 Paul Thomas <pault@gcc.gnu.org> gcc/fortran PR fortran/96312 * trans-expr.c (fcncall_realloc_result): Only compare shapes if lhs was allocated.. gcc/testsuite/ PR fortran/96312 * gfortran.dg/pr96312.f90: New test.
next prev parent reply other threads:[~2020-08-10 5:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-24 16:47 [Bug fortran/96312] New: " tkoenig at gcc dot gnu.org 2020-07-24 16:55 ` [Bug fortran/96312] " tkoenig at gcc dot gnu.org 2020-07-24 17:35 ` [Bug fortran/96312] [10/11 Regression] " tkoenig at gcc dot gnu.org 2020-07-24 17:35 ` tkoenig at gcc dot gnu.org 2020-07-24 17:51 ` tkoenig at gcc dot gnu.org 2020-07-24 18:18 ` dominiq at lps dot ens.fr 2020-07-25 8:59 ` tkoenig at gcc dot gnu.org 2020-07-25 9:18 ` tkoenig at gcc dot gnu.org 2020-08-08 15:01 ` pault at gcc dot gnu.org 2020-08-10 5:22 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-11 7:53 ` cvs-commit at gcc dot gnu.org 2020-08-11 8:04 ` 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-96312-4-rSDab0Ood2@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).