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/99369] [10/11 Regression] ICE in gfc_resolve_expr, at fortran/resolve.c:7167 Date: Thu, 25 Mar 2021 09:53:00 +0000 [thread overview] Message-ID: <bug-99369-4-S8L0nHWWbG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99369-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99369 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:c884ac1e743dbaaa5eea89ef95d5b987e66a28cb commit r10-9542-gc884ac1e743dbaaa5eea89ef95d5b987e66a28cb Author: Tobias Burnus <tobias@codesourcery.com> Date: Wed Mar 24 07:50:22 2021 +0100 Fortran: Extend buffer, use snprintf to avoid overflows [PR99369] gcc/fortran/ChangeLog: PR fortran/99369 * resolve.c (resolve_operator): Make 'msg' buffer larger and use snprintf. gcc/testsuite/ChangeLog: PR fortran/99369 * gfortran.dg/longnames.f90: New test. (cherry picked from commit b179026a5d9fcadadef6ca511933933672557495)
next prev parent reply other threads:[~2021-03-25 9:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-03 18:06 [Bug fortran/99369] New: " gscfq@t-online.de 2021-03-04 7:43 ` [Bug fortran/99369] " marxin at gcc dot gnu.org 2021-03-04 8:28 ` rguenth at gcc dot gnu.org 2021-03-04 8:39 ` gscfq@t-online.de 2021-03-04 8:42 ` marxin at gcc dot gnu.org 2021-03-22 20:56 ` anlauf at gcc dot gnu.org 2021-03-24 6:51 ` cvs-commit at gcc dot gnu.org 2021-03-25 9:53 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-25 9:54 ` burnus 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-99369-4-S8L0nHWWbG@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).