From: Matthieu Longo <matthieu.longo@arm.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v1] gdb: align siginfo_t with the Linux kernel definition
Date: Thu, 25 Jun 2026 10:55:02 +0100 [thread overview]
Message-ID: <442a4714-b2b6-41a8-b8c2-3ca4543e5ea3@arm.com> (raw)
In-Reply-To: <87zf0jwr23.fsf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On 24/06/2026 22:45, Thiago Jung Bauermann wrote:
> Hello Matthieu,
>
> Sorry for the delay in responding.
>
> Matthieu Longo <matthieu.longo@arm.com> writes:
>>> --- a/gdb/linux-tdep.c
>>> +++ b/gdb/linux-tdep.c
>>> @@ -293,6 +293,13 @@ linux_get_siginfo_type (struct gdbarch *gdbarch)
>>> struct type *uint32_type = builtin_types->builtin_uint32;
>>> void_ptr_type = lookup_pointer_type (builtin_type (gdbarch)->builtin_void);
>>> + /* Compute padding length, i.e. __ADDR_BND_PKEY_PAD. */
>>> + unsigned alignof_void_ptr = type_align (void_ptr_type);
>>> + unsigned padding_size = (alignof_void_ptr < sizeof(short)
>>> + ? sizeof(short)
>>> + : alignof_void_ptr);
>
> Nit: the two lines above are indented with spaces rather than tabs.
I don't understand why those lines should be using spaces instead of tabs.
See the attached screenshots.
You can see that the style I used is similar to existing ones in aarch64-linux-tdep.c or elsewhere.
Please can you clarify what you meant.
Matthieu
[-- Attachment #2: Screenshot 2026-06-25 102635.png --]
[-- Type: image/png, Size: 18125 bytes --]
[-- Attachment #3: Screenshot 2026-06-25 102328.png --]
[-- Type: image/png, Size: 28638 bytes --]
prev parent reply other threads:[~2026-06-25 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 10:16 Matthieu Longo
2026-06-12 10:42 ` Matthieu Longo
2026-06-17 6:07 ` Thiago Jung Bauermann
2026-06-17 9:11 ` Matthieu Longo
2026-06-18 3:02 ` Thiago Jung Bauermann
2026-06-18 14:02 ` Matthieu Longo
2026-06-18 16:23 ` Thiago Jung Bauermann
2026-06-19 3:58 ` Thiago Jung Bauermann
2026-06-19 10:45 ` Matthieu Longo
2026-06-22 8:42 ` Matthieu Longo
2026-06-24 21:45 ` Thiago Jung Bauermann
2026-06-25 9:55 ` Matthieu Longo [this message]
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=442a4714-b2b6-41a8-b8c2-3ca4543e5ea3@arm.com \
--to=matthieu.longo@arm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.org \
--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