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:42 +0000 [thread overview]
Message-ID: <bug-95090-4-LjX7Vtunng@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 #15 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:78c4b06ac3df51c460de835917549c8555ee4eaf
commit r10-8252-g78c4b06ac3df51c460de835917549c8555ee4eaf
Author: Harald Anlauf <anlauf@gmx.de>
Date: Fri May 29 21:19:31 2020 +0200
PR fortran/95090 - ICE: identifier overflow
The initial fix for this PR uncovered several latent issues with further
too small string buffers which showed up only when testing on i686.
Provide sufficiently large temporaries.
2020-05-29 Harald Anlauf <anlauf@gmx.de>
gcc/fortran/
PR fortran/95090
* class.c (get_unique_type_string): Enlarge temporary for
name-mangling. Use strncpy to prevent buffer overrun.
(get_unique_hashed_string): Enlarge temporary.
(gfc_hash_value): Enlarge temporary for name-mangling.
(cherry picked from commit 7deca8c0b3765787627b11387b56b97b01a8bf33)
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
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 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-LjX7Vtunng@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).