public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf 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: Tue, 26 May 2020 21:04:44 +0000 [thread overview] Message-ID: <bug-95090-4-NmDqyYa92E@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 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-05-26 CC| |anlauf at gcc dot gnu.org Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Priority|P3 |P4 --- Comment #1 from anlauf at gcc dot gnu.org --- Confirmed. The fix is to provide a sufficiently large buffer: diff --git a/gcc/fortran/iresolve.c b/gcc/fortran/iresolve.c index 7ecb6595f59..df4f2265c58 100644 --- a/gcc/fortran/iresolve.c +++ b/gcc/fortran/iresolve.c @@ -47,7 +47,8 @@ along with GCC; see the file COPYING3. If not see const char * gfc_get_string (const char *format, ...) { - char temp_name[128]; + /* Provide sufficient space to hold "_F.caf_token__symbol_MOD_symbol". */ + char temp_name[14 + GFC_MAX_SYMBOL_LEN + 5 + GFC_MAX_SYMBOL_LEN + 1]; const char *str; va_list ap; tree ident;
next prev parent reply other threads:[~2020-05-26 21:04 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 ` anlauf at gcc dot gnu.org [this message] 2020-05-27 19:20 ` [Bug fortran/95090] " 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 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-NmDqyYa92E@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).