Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Keith Seitz <keiths@redhat.com>
Subject: RE: [PATCH] gdb, btrace: support libipt v2.2 events
Date: Mon, 4 May 2026 07:16:13 +0000	[thread overview]
Message-ID: <DM8PR11MB574978C2C2333F2E449CDCFFDE312@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87pl3fgk3j.fsf@tromey.com>

Hello Tom,

>>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
>
>>> +	    std::string aux_string = std::string (_("trig: trbv = "))
>>> +	      + hex_string (event.variant.trig.trbv);
>
>Normally here we'd wrap the RSH in parens, per the coding standards.

I'd need to break at the =, then, like this:

	    std::string aux_string
	      = (std::string (_("trig: trbv = "))
		 + hex_string (event.variant.trig.trbv));

The patch matches the surrounding style, so if you want this fixed, I'd need
to fix it everywhere in a separate patch.


>>> +#endif /* (LIBIPT_VERSION >= 0x202) */
>
>Keith> Elsewhere in the file, this comment includes "defined".
>
>True but those spots seem to be in error.

I fixed those in a separate obvious patch:

diff --git a/gdb/btrace.c b/gdb/btrace.c
index f9c6f0e5b6a..ef152c531fb 100644
--- a/gdb/btrace.c
+++ b/gdb/btrace.c
@@ -1283,7 +1283,7 @@ decode_interrupt_vector (const uint8_t vector)
 
   return nullptr;
 }
-#endif /* defined (LIBIPT_VERSION >= 0x201) */
+#endif /* (LIBIPT_VERSION >= 0x201) */
 
 /* Handle instruction decode events (libipt-v2).  */
 
@@ -1596,7 +1596,7 @@ handle_pt_insn_events (struct btrace_thread_info *btinfo,
            handle_pt_aux_insn (btinfo, aux_string, pc);
            break;
          }
-#endif /* defined (LIBIPT_VERSION >= 0x201) */
+#endif /* (LIBIPT_VERSION >= 0x201) */
 
 #if (LIBIPT_VERSION >= 0x202)
        case ptev_trig:
@@ -3064,7 +3064,7 @@ pt_print_packet (const struct pt_packet *packet)
                  packet->payload.ptw.payload,
                  packet->payload.ptw.ip ? (" ip") : (""));
       break;
-#endif /* defined (LIBIPT_VERSION >= 0x200)  */
+#endif /* (LIBIPT_VERSION >= 0x200)  */
 
 #if (LIBIPT_VERSION >= 0x201)
     case ppt_cfe:
@@ -3077,7 +3077,7 @@ pt_print_packet (const struct pt_packet *packet)
       gdb_printf (("evd %u: 0x%" PRIx64 ""), packet->payload.evd.type,
                  packet->payload.evd.payload);
       break;
-#endif /* defined (LIBIPT_VERSION >= 0x201)  */
+#endif /* (LIBIPT_VERSION >= 0x201)  */
     }
 }

Markus.
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  reply	other threads:[~2026-05-04  7:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 11:24 Markus Metzger
2026-04-30 18:11 ` Keith Seitz
2026-05-01 16:39   ` Tom Tromey
2026-05-04  7:16     ` Metzger, Markus T [this message]
2026-05-04 16:08       ` Simon Marchi
2026-05-05 13:28       ` Tom Tromey
2026-05-08  5:07         ` Metzger, Markus T
2026-05-04  7:16   ` Metzger, Markus T

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=DM8PR11MB574978C2C2333F2E449CDCFFDE312@DM8PR11MB5749.namprd11.prod.outlook.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tom@tromey.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