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/95090] ICE: identifier overflow: 129
Date: Fri, 05 Jun 2020 19:32:37 +0000 [thread overview]
Message-ID: <bug-95090-4-rvWJEpw2TM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95090-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95090
--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:2ee8913bbbb0c278169b18b0123316ea4745120f
commit r10-8251-g2ee8913bbbb0c278169b18b0123316ea4745120f
Author: Harald Anlauf <anlauf@gmx.de>
Date: Wed May 27 21:20:24 2020 +0200
PR fortran/95090 - ICE: identifier overflow
For long module name, derive type and component name, the generated
name-mangled symbol did not fit into a buffer when coarrays were
enabled. Provide sufficiently large temporary.
2020-05-27 Harald Anlauf <anlauf@gmx.de>
gcc/fortran/
PR fortran/95090
* iresolve.c (gfc_get_string): Enlarge temporary for
name-mangling.
gcc/testsuite/
PR fortran/95090
* gfortran.dg/pr95090.f90: New test.
(cherry picked from commit c949ec9c4e88d2ff6dbd5b179abddf3703129577)
next prev parent reply other threads:[~2020-06-05 19:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:43 [Bug fortran/95090] New: " gscfq@t-online.de
2020-05-26 21:04 ` [Bug fortran/95090] " anlauf at gcc dot gnu.org
2020-05-27 19:20 ` cvs-commit at gcc dot gnu.org
2020-05-27 19:22 ` anlauf at gcc dot gnu.org
2020-05-28 8:39 ` manfred99 at gmx dot ch
2020-05-28 9:31 ` manfred99 at gmx dot ch
2020-05-28 17:26 ` anlauf at gcc dot gnu.org
2020-05-28 18:50 ` anlauf at gcc dot gnu.org
2020-05-28 23:36 ` manfred99 at gmx dot ch
2020-05-29 10:58 ` manfred99 at gmx dot ch
2020-05-29 14:33 ` manfred99 at gmx dot ch
2020-05-29 18:49 ` anlauf at gcc dot gnu.org
2020-05-29 19:19 ` cvs-commit at gcc dot gnu.org
2020-05-30 18:51 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 20:53 ` 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-95090-4-rvWJEpw2TM@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: link
Be 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).