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/95707] ICE in finish_equivalences, at fortran/trans-common.c:1319 Date: Sat, 20 Jun 2020 14:15:34 +0000 [thread overview] Message-ID: <bug-95707-4-OvqLtHr349@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95707-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95707 --- Comment #3 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:3345e74299687de6144b87c0632018cafd4ccf3b commit r11-1570-g3345e74299687de6144b87c0632018cafd4ccf3b Author: Harald Anlauf <anlauf@gmx.de> Date: Sat Jun 20 16:15:16 2020 +0200 PR fortran/95707 - ICE in finish_equivalences, at fortran/trans-common.c:1319 With submodules and equivalence declarations, name mangling may result in long internal symbols overflowing internal buffers. We now check that we do not exceed the enlarged buffer sizes. gcc/fortran/ PR fortran/95707 * gfortran.h (gfc_common_head): Enlarge buffer. * trans-common.c (gfc_sym_mangled_common_id): Enlarge temporary buffers, and add check on length on mangled name to prevent overflow.
next prev parent reply other threads:[~2020-06-20 14:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-16 18:51 [Bug fortran/95707] New: " gscfq@t-online.de 2020-06-16 20:15 ` [Bug fortran/95707] " anlauf at gcc dot gnu.org 2020-06-17 19:28 ` anlauf at gcc dot gnu.org 2020-06-20 14:15 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-22 19:30 ` cvs-commit at gcc dot gnu.org 2020-06-23 20:47 ` 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-95707-4-OvqLtHr349@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).