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/95537] [11 regression] gfortran.dg/pr95090.f90 since r11-670 Date: Fri, 05 Jun 2020 19:32:53 +0000 [thread overview] Message-ID: <bug-95537-4-ZUFEUWerW2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95537-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95537 --- Comment #10 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:36442ee216acbe9a345ae625be53efbde8626477 commit r10-8254-g36442ee216acbe9a345ae625be53efbde8626477 Author: Harald Anlauf <anlauf@gmx.de> Date: Fri Jun 5 20:30:34 2020 +0200 PR fortran/95530, PR fortran/95537 - Buffer overflows with long symbols The testcases for PR95090 and PR95106 trigger buffer overflows with long symbols that were found with an instrumented compiler. Enlarge the affected buffers, and add checks that the buffers will suffice. 2020-06-05 Harald Anlauf <anlauf@gmx.de> gcc/fortran/ PR fortran/95530 PR fortran/95537 * decl.c (gfc_match_decl_type_spec): Enlarge buffer, and enhance string copy to detect buffer overflow. * gfortran.h (gfc_common_head): Enlarge buffer. * trans-common.c (finish_equivalences): Enhance string copy to detect buffer overflow. (cherry picked from commit bcd96c9cce962ca5b2c6f8459597fb759f945ccf)
next prev parent reply other threads:[~2020-06-05 19:32 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-04 16:32 [Bug fortran/95537] New: " seurer at linux dot vnet.ibm.com 2020-06-04 16:33 ` [Bug fortran/95537] " seurer at linux dot vnet.ibm.com 2020-06-04 17:24 ` anlauf at gcc dot gnu.org 2020-06-04 20:19 ` seurer at linux dot vnet.ibm.com 2020-06-04 20:55 ` anlauf at gcc dot gnu.org 2020-06-04 21:13 ` seurer at linux dot vnet.ibm.com 2020-06-04 21:21 ` anlauf at gcc dot gnu.org 2020-06-04 21:24 ` seurer at linux dot vnet.ibm.com 2020-06-04 22:29 ` seurer at linux dot vnet.ibm.com 2020-06-05 6:30 ` rguenth at gcc dot gnu.org 2020-06-05 18:30 ` cvs-commit at gcc dot gnu.org 2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-05 20:35 ` cvs-commit at gcc dot gnu.org 2020-06-05 20:38 ` 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-95537-4-ZUFEUWerW2@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).