From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH v2 0/5] Fix and cleanups in jit.c
Date: Mon, 16 Dec 2019 03:39:00 -0000 [thread overview]
Message-ID: <20191216033917.2936248-1-simon.marchi@polymtl.ca> (raw)
This is a follow-up to:
https://sourceware.org/ml/gdb-patches/2019-12/msg00568.html
Again, the first patch is a fix and the rest is some c++ification.
I think I fixed all review comments from v1, the biggest change being
the use of std::forward_list instead of std::vector.
Simon Marchi (5):
Fix double-free when creating more than one block in JIT debug info
reader
jit: c++-ify gdb_symtab
jit: make gdb_object::symtabs an std::forward_list
jit: c++-ify gdb_block
jit: make gdb_symtab::blocks an std::forward_list
gdb/jit.c | 207 ++++++++++----------------
gdb/testsuite/gdb.base/jit-reader.exp | 14 +-
gdb/testsuite/gdb.base/jithost.c | 45 ++++--
gdb/testsuite/gdb.base/jithost.h | 15 +-
gdb/testsuite/gdb.base/jitreader.c | 34 +++--
5 files changed, 158 insertions(+), 157 deletions(-)
--
2.24.1
next reply other threads:[~2019-12-16 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 3:39 Simon Marchi [this message]
2019-12-16 3:39 ` [PATCH v2 2/5] jit: c++-ify gdb_symtab Simon Marchi
2019-12-16 3:39 ` [PATCH v2 5/5] jit: make gdb_symtab::blocks an std::forward_list Simon Marchi
2019-12-16 3:39 ` [PATCH v2 3/5] jit: make gdb_object::symtabs " Simon Marchi
2019-12-16 3:39 ` [PATCH v2 1/5] Fix double-free when creating more than one block in JIT debug info reader Simon Marchi
2019-12-16 3:57 ` [PATCH v2 4/5] jit: c++-ify gdb_block Simon Marchi
2019-12-16 19:27 ` [PATCH v2 0/5] Fix and cleanups in jit.c Pedro Alves
2019-12-16 23:19 ` Simon Marchi
2019-12-17 19:10 ` Pedro Alves
2019-12-17 19:32 ` Simon Marchi
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=20191216033917.2936248-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.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