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/94788] [8/9 Regression] Severe regression leading to double free in tcache Date: Sat, 02 May 2020 15:33:48 +0000 [thread overview] Message-ID: <bug-94788-4-Hv9Stjq3pQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94788-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94788 --- Comment #43 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Thomas Kथà¤nig <tkoenig@gcc.gnu.org>: https://gcc.gnu.org/g:116784bbde9ed391393320d936ae2fff37442779 commit r11-25-g116784bbde9ed391393320d936ae2fff37442779 Author: Thomas Koenig <tkoenig@gcc.gnu.org> Date: Sat May 2 17:30:01 2020 +0200 Add asan subdirectory for gfortran.dg. Because the test case for PR 94788 requires -fsanitize=address to expose the double free, I have created a subdirectory under gfortran.dg where such test cases can go. I have tested this with make check-fortran RUNTESTFLAGS="asan.exp=*" and it works; with a compiler that introduces the double free bug into the test case, the result is as expected 2020-05-02 Thomas Koenig <tkoenig@gcc.gnu.org> PR fortran/94788 * gfortran.dg/asan: New directory. * gfortran.dg/asan/asan.exp: New file. * gfortran.dg/asan/pointer_assign_16.f90: New test case.
next prev parent reply other threads:[~2020-05-02 15:33 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-27 8:38 [Bug fortran/94788] New: " juergen.reuter at desy dot de 2020-04-27 8:38 ` [Bug fortran/94788] " juergen.reuter at desy dot de 2020-04-27 9:46 ` juergen.reuter at desy dot de 2020-04-27 10:27 ` [Bug fortran/94788] [10 Regression] " rguenth at gcc dot gnu.org 2020-04-27 10:41 ` juergen.reuter at desy dot de 2020-04-27 12:19 ` juergen.reuter at desy dot de 2020-04-27 12:49 ` simon.brass at desy dot de 2020-04-27 17:09 ` simon.brass at desy dot de 2020-04-27 17:26 ` tkoenig at gcc dot gnu.org 2020-04-27 17:36 ` juergen.reuter at desy dot de 2020-04-27 18:30 ` tkoenig at gcc dot gnu.org 2020-04-27 19:26 ` juergen.reuter at desy dot de 2020-04-27 19:33 ` juergen.reuter at desy dot de 2020-04-27 20:39 ` juergen.reuter at desy dot de 2020-04-27 20:40 ` juergen.reuter at desy dot de 2020-04-27 20:40 ` juergen.reuter at desy dot de 2020-04-27 21:15 ` juergen.reuter at desy dot de 2020-04-27 21:38 ` tkoenig at gcc dot gnu.org 2020-04-27 21:51 ` cvs-commit at gcc dot gnu.org 2020-04-27 21:55 ` [Bug fortran/94788] [8/9 " tkoenig at gcc dot gnu.org 2020-04-27 22:02 ` juergen.reuter at desy dot de 2020-04-27 22:23 ` kargl at gcc dot gnu.org 2020-04-27 22:33 ` juergen.reuter at desy dot de 2020-04-28 5:57 ` tkoenig at gcc dot gnu.org 2020-04-28 8:02 ` burnus at gcc dot gnu.org 2020-04-28 8:12 ` juergen.reuter at desy dot de 2020-04-28 8:17 ` juergen.reuter at desy dot de 2020-04-28 9:13 ` tkoenig at gcc dot gnu.org 2020-04-28 11:17 ` juergen.reuter at desy dot de 2020-04-28 11:36 ` juergen.reuter at desy dot de 2020-04-28 14:06 ` juergen.reuter at desy dot de 2020-04-29 0:38 ` juergen.reuter at desy dot de 2020-04-29 9:09 ` juergen.reuter at desy dot de 2020-04-29 18:32 ` tkoenig at gcc dot gnu.org 2020-04-29 21:58 ` juergen.reuter at desy dot de 2020-04-30 16:31 ` tkoenig at gcc dot gnu.org 2020-04-30 16:35 ` juergen.reuter at desy dot de 2020-04-30 16:49 ` tkoenig at gcc dot gnu.org 2020-04-30 17:37 ` juergen.reuter at desy dot de 2020-04-30 17:38 ` juergen.reuter at desy dot de 2020-05-01 12:27 ` tkoenig at gcc dot gnu.org 2020-05-01 12:53 ` cvs-commit at gcc dot gnu.org 2020-05-01 12:55 ` cvs-commit at gcc dot gnu.org 2020-05-02 15:33 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-02 19:51 ` cvs-commit at gcc dot gnu.org 2020-05-21 10:42 ` tkoenig 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-94788-4-Hv9Stjq3pQ@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).