From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Rewrite enum_flags, add unit tests, fix problems
Date: Fri, 21 Aug 2020 15:45:20 +0100 [thread overview]
Message-ID: <20200821144523.19451-1-pedro@palves.net> (raw)
This is an update of a version of this series that I posted back in
2016:
[PATCH 0/3] enum_flags: Fix problems and add comprehensive unit tests
https://sourceware.org/legacy-ml/gdb-patches/2016-11/msg00079.html
But I never followed thorough with it, leaving it collecting dust on
my github. Over the following years, I polished it and tweaked it
further and extended the unit tests, but never managed to re-submit it
all upstream.
Since the subject of enum_flags came up again this week, I thought I'd
try it again. This is the result.
Pedro Alves (3):
Rewrite valid-expr.h's internals in terms of the detection idiom
(C++17/N4502)
Use type_instance_flags more throughout
Rewrite enum_flags, add unit tests, fix problems
gdb/Makefile.in | 1 +
gdb/btrace.c | 4 +-
gdb/compile/compile-c-types.c | 3 +-
gdb/compile/compile-cplus-symbols.c | 4 +-
gdb/compile/compile-cplus-types.c | 10 +-
gdb/dwarf2/read.c | 7 +-
gdb/eval.c | 2 +-
gdb/gdbarch.c | 6 +-
gdb/gdbarch.h | 12 +-
gdb/gdbarch.sh | 8 +-
gdb/gdbtypes.c | 58 ++--
gdb/gdbtypes.h | 15 +-
gdb/go-exp.y | 2 +-
gdb/record-btrace.c | 10 +-
gdb/stabsread.c | 2 +-
gdb/type-stack.c | 4 +-
gdb/unittests/enum-flags-selftests.c | 586 +++++++++++++++++++++++++++++++++++
gdbsupport/enum-flags.h | 366 +++++++++++++++++-----
gdbsupport/traits.h | 67 ++++
gdbsupport/valid-expr.h | 35 ++-
20 files changed, 1035 insertions(+), 167 deletions(-)
create mode 100644 gdb/unittests/enum-flags-selftests.c
base-commit: b70e516e89d95d06252cb04ded3397ec0a0a3212
--
2.14.5
next reply other threads:[~2020-08-21 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 14:45 Pedro Alves [this message]
2020-08-21 14:45 ` [PATCH 1/3] Rewrite valid-expr.h's internals in terms of the detection idiom (C++17/N4502) Pedro Alves
2020-09-28 18:59 ` Tom Tromey
2020-09-28 19:58 ` Luis Machado via Gdb-patches
2020-09-28 20:00 ` Tom Tromey
2020-09-29 13:04 ` Tom Tromey
2020-09-29 19:24 ` Pedro Alves
2020-09-29 22:50 ` [pushed] Tweak gdbsupport/valid-expr.h for GCC 6, fix build (Re: [PATCH 1/3] Rewrite valid-expr.h's internals in terms of the detection idiom (C++17/N4502)) Pedro Alves
2020-08-21 14:45 ` [PATCH 2/3] Use type_instance_flags more throughout Pedro Alves
2020-08-25 11:36 ` Luis Machado
2020-09-14 11:56 ` Pedro Alves
2020-08-26 10:06 ` Andrew Burgess
2020-09-14 12:54 ` Pedro Alves
2020-08-26 15:21 ` Andrew Burgess
2020-09-14 13:53 ` Pedro Alves
2020-09-11 20:21 ` Tom Tromey
2020-09-14 19:26 ` Pedro Alves
2020-08-21 14:45 ` [PATCH 3/3] Rewrite enum_flags, add unit tests, fix problems Pedro Alves
2020-08-21 15:51 ` [PATCH 0/3] " Andrew Burgess
2020-09-11 20:26 ` Tom Tromey
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=20200821144523.19451-1-pedro@palves.net \
--to=pedro@palves.net \
--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