public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/63854] Fix memory leaks seen in JIT
Date: Mon, 01 Dec 2014 16:14:00 -0000	[thread overview]
Message-ID: <bug-63854-4-3dir78S9N0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63854-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63854

--- Comment #20 from dmalcolm at gcc dot gnu.org ---
Author: dmalcolm
Date: Mon Dec  1 16:13:29 2014
New Revision: 218227

URL: https://gcc.gnu.org/viewcvs?rev=218227&root=gcc&view=rev
Log:
PR jit/63854: Add support for running "make check-jit" under valgrind

gcc/testsuite/ChangeLog:
    PR jit/63854
    * jit.dg/jit.exp (report_leak): New.
    (parse_valgrind_logfile): New.
    (fixed_host_execute): Detect if RUN_UNDER_VALGRIND is present
    in the environment, and if so, run the executable under
    valgrind, capturing valgrind's output to a logfile.  Parse the
    log file, generating PASSes and XFAILs for the summary of leaks.
    Use "wait" before "close": valgrind might not have finished
    writing the log out before we parse it, so we need to wait for
    the spawnee to finish.


Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/jit.dg/jit.exp


  parent reply	other threads:[~2014-12-01 16:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 17:58 [Bug jit/63854] New: " dmalcolm at gcc dot gnu.org
2014-11-13 18:00 ` [Bug jit/63854] " dmalcolm at gcc dot gnu.org
2014-11-17 17:49 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:09 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:12 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:23 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:34 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:43 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:46 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:50 ` dmalcolm at gcc dot gnu.org
2014-11-19 19:57 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:10 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:14 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:18 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:21 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:27 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:32 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:43 ` dmalcolm at gcc dot gnu.org
2014-11-19 20:45 ` dmalcolm at gcc dot gnu.org
2014-12-01 16:14 ` dmalcolm at gcc dot gnu.org [this message]
2014-12-01 17:16 ` dmalcolm at gcc dot gnu.org
2014-12-01 17:29 ` dmalcolm at gcc dot gnu.org
2014-12-01 17:40 ` dmalcolm at gcc dot gnu.org
2014-12-04 21:11 ` dmalcolm at gcc dot gnu.org
2014-12-04 21:24 ` dmalcolm at gcc dot gnu.org
2014-12-09 20:47 ` dmalcolm at gcc dot gnu.org
2014-12-10 19:16 ` dmalcolm at gcc dot gnu.org
2014-12-11 15:07 ` dcb314 at hotmail dot com
2015-01-12 19:59 ` dmalcolm at gcc dot gnu.org
2015-04-16 14:08 ` ienkovich at gcc dot gnu.org
2020-08-21 13:26 ` cvs-commit at gcc dot gnu.org
2022-03-19 17:43 ` cvs-commit 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-63854-4-3dir78S9N0@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: link
Be 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).