From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 4/4] [gdb] Remove '/**<' comment marker
Date: Mon, 1 Jun 2026 12:53:38 +0200 [thread overview]
Message-ID: <20260601105338.2867566-5-tdevries@suse.de> (raw)
In-Reply-To: <20260601105338.2867566-1-tdevries@suse.de>
Another comment marker doxygen supports is "/**<". Replace it with "/*".
Suggested-By: Kevin Buettner <kevinb@redhat.com>
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34186
---
gdb/gdbtypes.h | 12 ++++++------
gdb/type-codes.def | 34 +++++++++++++++++-----------------
2 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/gdb/gdbtypes.h b/gdb/gdbtypes.h
index d08cf73711f..97adbe61db8 100644
--- a/gdb/gdbtypes.h
+++ b/gdb/gdbtypes.h
@@ -63,7 +63,7 @@ struct dwarf2_property_baton;
enum type_code
{
- TYPE_CODE_UNDEF = 0, /**< Not used; catches errors */
+ TYPE_CODE_UNDEF = 0, /* Not used; catches errors */
#define OP(X) X,
#include "type-codes.def"
@@ -483,12 +483,12 @@ struct dynamic_prop_list
enum field_loc_kind
{
- FIELD_LOC_KIND_BITPOS, /**< bitpos */
- FIELD_LOC_KIND_ENUMVAL, /**< enumval */
- FIELD_LOC_KIND_PHYSADDR, /**< physaddr */
- FIELD_LOC_KIND_PHYSNAME, /**< physname */
+ FIELD_LOC_KIND_BITPOS, /* bitpos */
+ FIELD_LOC_KIND_ENUMVAL, /* enumval */
+ FIELD_LOC_KIND_PHYSADDR, /* physaddr */
+ FIELD_LOC_KIND_PHYSNAME, /* physname */
/* A DWARF block that computes the address of the field. */
- FIELD_LOC_KIND_DWARF_BLOCK_ADDR, /**< dwarf_block */
+ FIELD_LOC_KIND_DWARF_BLOCK_ADDR, /* dwarf_block */
/* A DWARF block that computes the bit offset of the field. */
FIELD_LOC_KIND_DWARF_BLOCK_BITPOS,
};
diff --git a/gdb/type-codes.def b/gdb/type-codes.def
index ebc391c81ae..afd2b12d9ba 100644
--- a/gdb/type-codes.def
+++ b/gdb/type-codes.def
@@ -17,7 +17,7 @@
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>. */
-OP (TYPE_CODE_PTR) /**< Pointer type */
+OP (TYPE_CODE_PTR) /* Pointer type */
/* Array type with lower & upper bounds.
@@ -39,12 +39,12 @@ OP (TYPE_CODE_PTR) /**< Pointer type */
from right to left, not left to right. */
OP (TYPE_CODE_ARRAY)
-OP (TYPE_CODE_STRUCT) /**< C struct or Pascal record */
-OP (TYPE_CODE_UNION) /**< C union or Pascal variant part */
-OP (TYPE_CODE_ENUM) /**< Enumeration type */
-OP (TYPE_CODE_FLAGS) /**< Bit flags type */
-OP (TYPE_CODE_FUNC) /**< Function type */
-OP (TYPE_CODE_INT) /**< Integer type */
+OP (TYPE_CODE_STRUCT) /* C struct or Pascal record */
+OP (TYPE_CODE_UNION) /* C union or Pascal variant part */
+OP (TYPE_CODE_ENUM) /* Enumeration type */
+OP (TYPE_CODE_FLAGS) /* Bit flags type */
+OP (TYPE_CODE_FUNC) /* Function type */
+OP (TYPE_CODE_INT) /* Integer type */
/* Floating type. This is *NOT* a complex type. */
OP (TYPE_CODE_FLT)
@@ -57,8 +57,8 @@ OP (TYPE_CODE_FLT)
type is a generic pointer. */
OP (TYPE_CODE_VOID)
-OP (TYPE_CODE_SET) /**< Pascal sets */
-OP (TYPE_CODE_RANGE) /**< Range (integers within spec'd bounds). */
+OP (TYPE_CODE_SET) /* Pascal sets */
+OP (TYPE_CODE_RANGE) /* Range (integers within spec'd bounds). */
/* A string type which is like an array of character but prints
differently. It does not contain a length field as Pascal
@@ -72,7 +72,7 @@ OP (TYPE_CODE_STRING)
OP (TYPE_CODE_ERROR)
/* C++ */
-OP (TYPE_CODE_METHOD) /**< Method type */
+OP (TYPE_CODE_METHOD) /* Method type */
/* Pointer-to-member-function type. This describes how to access a
particular member function of a class (possibly a virtual
@@ -87,26 +87,26 @@ OP (TYPE_CODE_METHODPTR)
platforms). */
OP (TYPE_CODE_MEMBERPTR)
-OP (TYPE_CODE_REF) /**< C++ Reference types */
+OP (TYPE_CODE_REF) /* C++ Reference types */
-OP (TYPE_CODE_RVALUE_REF) /**< C++ rvalue reference types */
+OP (TYPE_CODE_RVALUE_REF) /* C++ rvalue reference types */
-OP (TYPE_CODE_CHAR) /**< *real* character type */
+OP (TYPE_CODE_CHAR) /* *real* character type */
/* Boolean type. 0 is false, 1 is true, and other values are
non-boolean (e.g. FORTRAN "logical" used as unsigned int). */
OP (TYPE_CODE_BOOL)
/* Fortran */
-OP (TYPE_CODE_COMPLEX) /**< Complex float */
+OP (TYPE_CODE_COMPLEX) /* Complex float */
OP (TYPE_CODE_TYPEDEF)
-OP (TYPE_CODE_NAMESPACE) /**< C++ namespace. */
+OP (TYPE_CODE_NAMESPACE) /* C++ namespace. */
-OP (TYPE_CODE_DECFLOAT) /**< Decimal floating point. */
+OP (TYPE_CODE_DECFLOAT) /* Decimal floating point. */
-OP (TYPE_CODE_MODULE) /**< Fortran module. */
+OP (TYPE_CODE_MODULE) /* Fortran module. */
/* Internal function type. */
OP (TYPE_CODE_INTERNAL_FUNCTION)
--
2.51.0
next prev parent reply other threads:[~2026-06-01 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 10:53 [PATCH v2 0/4] [gdb] Remove doxygen support Tom de Vries
2026-06-01 10:53 ` [PATCH v2 1/4] [gdb/doc] " Tom de Vries
2026-06-01 10:53 ` [PATCH v2 2/4] [gdb] Remove '/* *' multi-line comment marker Tom de Vries
2026-06-01 10:53 ` [PATCH v2 3/4] [gdb] Remove \page marker Tom de Vries
2026-06-01 10:53 ` Tom de Vries [this message]
2026-06-01 16:16 ` [PATCH v2 0/4] [gdb] Remove doxygen support 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=20260601105338.2867566-5-tdevries@suse.de \
--to=tdevries@suse.de \
--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