Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>,
	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 12:08:15 -0400	[thread overview]
Message-ID: <a50d8ba4-e11a-4d98-9e2f-147b40148923@simark.ca> (raw)
In-Reply-To: <DM8PR11MB574978C2C2333F2E449CDCFFDE312@DM8PR11MB5749.namprd11.prod.outlook.com>

On 5/4/26 3:16 AM, Metzger, Markus T wrote:
> 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.

Just noting that you could also use `string_printf` for this, which
sometimes gives more readable code than using concatenation (and
perhaps one day we'll use {fmt}/std::format, one can dream).

Simon

  reply	other threads:[~2026-05-04 16:08 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
2026-05-04 16:08       ` Simon Marchi [this message]
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=a50d8ba4-e11a-4d98-9e2f-147b40148923@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=markus.t.metzger@intel.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