From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH v2 3/8] gdbsupport: add type definitions for pid, lwp and tid
Date: Thu, 5 Jan 2023 15:02:32 -0500 [thread overview]
Message-ID: <20230105200237.987771-4-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20230105200237.987771-1-simon.marchi@polymtl.ca>
From: Simon Marchi <simon.marchi@efficios.com>
A following patch will want to declare variables of the same type as
some ptid_t components. To make that easy (and avoid harcoding those
types everywhere), define some type definitions in the ptid_t struct for
each of them. Use them throughout ptid.h.
I initially used pid_t, lwp_t and tid_t, but there is the risk of some
system defining the pid_t type using a macro instead of a typedef, which
would break things. So, use the _type suffix instead.
Change-Id: I820b0bea9dafcb4914f1c9ba4bb96b5c666c8dec
Approved-By: Andrew Burgess <aburgess@redhat.com>
---
gdbsupport/ptid.h | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/gdbsupport/ptid.h b/gdbsupport/ptid.h
index 365e11c6db5e..aa296b83181c 100644
--- a/gdbsupport/ptid.h
+++ b/gdbsupport/ptid.h
@@ -39,6 +39,10 @@
class ptid_t
{
public:
+ using pid_type = int;
+ using lwp_type = long;
+ using tid_type = ULONGEST;
+
/* Must have a trivial defaulted default constructor so that the
type remains POD. */
ptid_t () noexcept = default;
@@ -48,13 +52,13 @@ class ptid_t
A ptid with only a PID (LWP and TID equal to zero) is usually used to
represent a whole process, including all its lwps/threads. */
- explicit constexpr ptid_t (int pid, long lwp = 0, ULONGEST tid = 0)
+ explicit constexpr ptid_t (pid_type pid, lwp_type lwp = 0, tid_type tid = 0)
: m_pid (pid), m_lwp (lwp), m_tid (tid)
{}
/* Fetch the pid (process id) component from the ptid. */
- constexpr int pid () const
+ constexpr pid_type pid () const
{ return m_pid; }
/* Return true if the ptid's lwp member is non-zero. */
@@ -64,7 +68,7 @@ class ptid_t
/* Fetch the lwp (lightweight process) component from the ptid. */
- constexpr long lwp () const
+ constexpr lwp_type lwp () const
{ return m_lwp; }
/* Return true if the ptid's tid member is non-zero. */
@@ -74,7 +78,7 @@ class ptid_t
/* Fetch the tid (thread id) component from a ptid. */
- constexpr ULONGEST tid () const
+ constexpr tid_type tid () const
{ return m_tid; }
/* Return true if the ptid represents a whole process, including all its
@@ -144,13 +148,13 @@ class ptid_t
private:
/* Process id. */
- int m_pid;
+ pid_type m_pid;
/* Lightweight process id. */
- long m_lwp;
+ lwp_type m_lwp;
/* Thread id. */
- ULONGEST m_tid;
+ tid_type m_tid;
};
/* Functor to hash a ptid. */
--
2.39.0
next prev parent reply other threads:[~2023-01-05 20:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 20:02 [PATCH v2 0/8] Initial support for ROCm platform (AMD GPU) debugging Simon Marchi
2023-01-05 20:02 ` [PATCH v2 1/8] gdb: add supports_arch_info callback to gdbarch_register Simon Marchi
2023-01-05 20:02 ` [PATCH v2 2/8] gdb: make install_breakpoint return a non-owning reference Simon Marchi
2023-01-05 20:02 ` Simon Marchi [this message]
2023-01-05 20:02 ` [PATCH v2 4/8] gdb: add inferior_pre_detach observable Simon Marchi
2023-01-05 20:02 ` [PATCH v2 5/8] gdb: add gdbarch_up Simon Marchi
2023-01-05 20:31 ` Tom Tromey
2023-01-05 20:36 ` Simon Marchi
2023-01-05 20:41 ` Tom Tromey
2023-01-06 0:48 ` Simon Marchi
2023-01-05 20:02 ` [PATCH v2 6/8] gdb/solib-svr4: don't disable probes interface if probe not found Simon Marchi
2023-01-05 20:02 ` [PATCH v2 7/8] gdb: make gdb_printing_disassembler::stream public Simon Marchi
2023-01-05 20:02 ` [PATCH v2 8/8] gdb: initial support for ROCm platform (AMDGPU) debugging Simon Marchi
2023-01-05 20:17 ` Simon Marchi
2023-01-25 17:03 ` [PATCH v2 0/8] Initial support for ROCm platform (AMD GPU) debugging Simon Marchi
2023-02-02 15:08 ` Simon Marchi
2023-02-06 11:47 ` Tom de Vries
2023-02-06 14:01 ` Lancelot Six
2023-02-06 16:53 ` Tom de Vries
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=20230105200237.987771-4-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
/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).