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/100297] FAIL: gfortran.dg/allocatable_function_1.f90 gfortran.dg/reshape_8.f90 Date: Thu, 29 Jun 2023 19:50:20 +0000 [thread overview] Message-ID: <bug-100297-4-fM8khIqa4b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100297-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100297 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:1a023e688186ea4cd284f5d269f2ecde9f80438c commit r13-7501-g1a023e688186ea4cd284f5d269f2ecde9f80438c Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Apr 18 21:24:20 2023 +0200 testsuite: fix scan-tree-dump patterns [PR83904,PR100297] Adjust scan-tree-dump patterns so that they do not accidentally match a valid path. gcc/testsuite/ChangeLog: PR testsuite/83904 PR fortran/100297 * gfortran.dg/allocatable_function_1.f90: Use "__builtin_free " instead of the naive "free". * gfortran.dg/reshape_8.f90: Extend pattern from a simple "data". (cherry picked from commit 6fc8e25cb6b5d720bedd85194b0ad740d75082f4)
prev parent reply other threads:[~2023-06-29 19:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-27 20:47 [Bug fortran/100297] New: " msebor at gcc dot gnu.org 2021-04-27 20:51 ` [Bug fortran/100297] " msebor at gcc dot gnu.org 2023-04-16 21:10 ` anlauf at gcc dot gnu.org 2023-04-16 22:12 ` schwab@linux-m68k.org 2023-04-17 19:24 ` anlauf at gcc dot gnu.org 2023-04-19 16:37 ` cvs-commit at gcc dot gnu.org 2023-04-19 16:45 ` anlauf at gcc dot gnu.org 2023-06-29 19:50 ` cvs-commit at gcc dot gnu.org [this message]
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-100297-4-fM8khIqa4b@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).