From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Mark Wielaard <mark@klomp.org>, "Frank Ch . Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org, Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH v3 0/4] Add Memory Sanitizer support
Date: Mon, 13 Feb 2023 17:45:47 +0100 [thread overview]
Message-ID: <20230213164551.550400-1-iii@linux.ibm.com> (raw)
Hi,
I've made a few more updates, as described in the changelog below.
Please take a look.
v2: https://sourceware.org/pipermail/elfutils-devel/2023q1/005868.html
v2 -> v3:
* Drop the integrated patches.
* Fix all backends with respect to returning references and rvalue
references; add a test.
* Apply Mark's suggestions to the printversion patch.
v1: https://sourceware.org/pipermail/elfutils-devel/2023q1/005831.html
v1 -> v2:
* Drop the unnecessary and the integrated patches.
* Add a comment to the xdefault_pattern patch.
* Add extern to the printversion patch.
* Use the fix from Mark for the handle_bit_registers() issue.
* Fix the --disable-demangle default value.
Best regards,
Ilya
Ilya Leoshkevich (4):
tests: Ignore dwfl-report-offline-memory
printversion: Fix unused variable
backends: Support returning lvalue and rvalue references
configure: Add --enable-sanitize-memory
backends/aarch64_retval.c | 5 ++---
backends/alpha_retval.c | 5 ++---
backends/arm_retval.c | 5 ++---
backends/i386_retval.c | 5 ++---
backends/ia64_retval.c | 5 ++---
backends/libebl_CPU.h | 15 ++++++++++++++
backends/m68k_retval.c | 5 ++---
backends/ppc64_retval.c | 5 ++---
backends/ppc_retval.c | 5 ++---
backends/riscv_retval.c | 5 ++---
backends/s390_retval.c | 5 ++---
backends/sh_retval.c | 5 ++---
backends/sparc_retval.c | 5 ++---
backends/x86_64_retval.c | 7 +++----
configure.ac | 35 +++++++++++++++++++++++++++++++--
debuginfod/Makefile.am | 3 ++-
debuginfod/debuginfod.cxx | 3 +--
lib/printversion.h | 5 ++++-
libasm/Makefile.am | 3 ++-
libdw/Makefile.am | 3 ++-
libelf/Makefile.am | 3 ++-
tests/.gitignore | 2 ++
tests/Makefile.am | 18 +++++++++++++++--
tests/funcretval_test++11.cxx | 37 +++++++++++++++++++++++++++++++++++
tests/run-funcretval++11.sh | 21 ++++++++++++++++++++
tests/run-readelf-self.sh | 5 +++++
tests/run-strip-reloc.sh | 5 +++++
tests/run-varlocs-self.sh | 5 +++++
28 files changed, 179 insertions(+), 51 deletions(-)
create mode 100644 tests/funcretval_test++11.cxx
create mode 100755 tests/run-funcretval++11.sh
--
2.39.1
next reply other threads:[~2023-02-13 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:45 Ilya Leoshkevich [this message]
2023-02-13 16:45 ` [PATCH v3 1/4] tests: Ignore dwfl-report-offline-memory Ilya Leoshkevich
2023-02-14 13:38 ` (subset) " Mark Wielaard
2023-02-13 16:45 ` [PATCH v3 2/4] printversion: Fix unused variable Ilya Leoshkevich
2023-02-14 13:42 ` (subset) " Mark Wielaard
2023-02-13 16:45 ` [PATCH v3 3/4] backends: Support returning lvalue and rvalue references Ilya Leoshkevich
2023-02-14 14:16 ` Mark Wielaard
2023-02-13 16:45 ` [PATCH v3 4/4] configure: Add --enable-sanitize-memory Ilya Leoshkevich
2023-02-14 14:25 ` Mark Wielaard
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=20230213164551.550400-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mark@klomp.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).