From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] Introduce scoped_restore_signal
Date: Thu, 17 Jun 2021 15:57:07 +0100 [thread overview]
Message-ID: <84b8034c-9f79-9774-dbfc-cf8d4935b62b@palves.net> (raw)
In-Reply-To: <20210615111429.1879286-3-pedro@palves.net>
On 2021-06-15 12:14 p.m., Pedro Alves wrote:
> +/* Simple wrapper that allows lazy initialization / destruction of T.
> + Slightly more efficient than gdb::optional, because it doesn't
> + carry storage to track whether the object has been initialized. */
> +template<typename T>
> +class lazy_init
> +{
> +public:
> + void emplace ()
> + {
> + new (m_buf) T ();
> + }
> +
> + void reset ()
> + {
> + reinterpret_cast <T *> (m_buf)->~T ();
> + }
> +
> +private:
> + alignas (T) gdb_byte m_buf[sizeof (T)];
> +};
> +
I was looking at this again, and realized that a raw buffer like that isn't super
convenient when you're debugging gdb and want to inspect T (you'll need to cast).
So I made it a union instead (see below). It has the added advantage that no cast
is necessary.
I'm going to push the series with this change.
diff --git c/gdbsupport/scoped_ignore_sigttou.h w/gdbsupport/scoped_ignore_sigttou.h
index 7b29f2b79a3..1fc8f80d7fd 100644
--- c/gdbsupport/scoped_ignore_sigttou.h
+++ w/gdbsupport/scoped_ignore_sigttou.h
@@ -34,16 +34,23 @@ class lazy_init
public:
void emplace ()
{
- new (m_buf) T ();
+ new (&m_u.obj) T ();
}
void reset ()
{
- reinterpret_cast <T *> (m_buf)->~T ();
+ m_u.obj.~T ();
}
private:
- alignas (T) gdb_byte m_buf[sizeof (T)];
+ union u
+ {
+ /* Must define ctor/dtor if T has non-trivial ctor/dtor. */
+ u () {}
+ ~u () {}
+
+ T obj;
+ } m_u;
};
next prev parent reply other threads:[~2021-06-17 15:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 11:14 [PATCH 0/4] Introduce scoped_ignore_signal & make it thread safe Pedro Alves
2021-06-15 11:14 ` [PATCH 1/4] Move scoped_ignore_sigttou to gdbsupport/ Pedro Alves
2021-06-15 11:14 ` [PATCH 2/4] Introduce scoped_restore_signal Pedro Alves
2021-06-17 14:57 ` Pedro Alves [this message]
2021-06-15 11:14 ` [PATCH 3/4] scoped_ignore_signal: Use sigprocmask+sigtimedwait instead of signal Pedro Alves
2021-06-26 12:35 ` Simon Marchi via Gdb-patches
2021-06-26 13:41 ` John Baldwin
2021-06-26 19:10 ` Simon Marchi via Gdb-patches
2021-06-27 14:55 ` Pedro Alves
2021-06-27 19:01 ` Simon Marchi via Gdb-patches
2021-06-15 11:14 ` [PATCH 4/4] Add a unit test for scoped_ignore_sigpipe Pedro Alves
2021-06-15 22:26 ` Lancelot SIX via Gdb-patches
2021-06-17 13:00 ` Pedro Alves
2021-06-15 17:04 ` [PATCH 0/4] Introduce scoped_ignore_signal & make it thread safe John Baldwin
2021-06-17 14:38 ` Pedro Alves
2021-06-17 15:36 ` Pedro Alves
2021-06-17 16:45 ` John Baldwin
2021-06-17 18:44 ` [pushed] Don't call sigtimedwait for scoped_ignore_sigttou Pedro Alves
2021-06-15 20:16 ` [PATCH 0/4] Introduce scoped_ignore_signal & make it thread safe 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=84b8034c-9f79-9774-dbfc-cf8d4935b62b@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