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/101514] ICE: out of memory allocating 18446744073709551600 bytes Date: Wed, 21 Jul 2021 16:54:25 +0000 [thread overview] Message-ID: <bug-101514-4-v2v5YJRfZK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101514-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101514 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:c2b15fe27e6a0e42b108111d51acce69628593b4 commit r12-2439-gc2b15fe27e6a0e42b108111d51acce69628593b4 Author: Harald Anlauf <anlauf@gmx.de> Date: Wed Jul 21 18:54:00 2021 +0200 Fortran: ICE, OOM while calculating sizes of derived type array components gcc/fortran/ChangeLog: PR fortran/101514 * target-memory.c (gfc_interpret_derived): Size of array component of derived type can only be computed here for explicit shape. * trans-types.c (gfc_get_nodesc_array_type): Do not dereference NULL pointers. gcc/testsuite/ChangeLog: PR fortran/101514 * gfortran.dg/pr101514.f90: New test.
next prev parent reply other threads:[~2021-07-21 16:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-19 17:26 [Bug fortran/101514] New: " gscfq@t-online.de 2021-07-20 9:45 ` [Bug fortran/101514] " rguenth at gcc dot gnu.org 2021-07-20 18:28 ` anlauf at gcc dot gnu.org 2021-07-20 19:50 ` anlauf at gcc dot gnu.org 2021-07-21 16:54 ` cvs-commit at gcc dot gnu.org [this message] 2021-07-28 19:13 ` cvs-commit at gcc dot gnu.org 2021-07-30 20:13 ` cvs-commit at gcc dot gnu.org 2021-07-30 20:14 ` 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-101514-4-v2v5YJRfZK@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).