From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add two new warnings to warning.m4
Date: Fri, 5 Jun 2026 23:13:33 +0200 [thread overview]
Message-ID: <1e125dd7-c1e2-40c7-9ee4-63cdaa0f93e1@suse.de> (raw)
In-Reply-To: <87fr30hft5.fsf@tromey.com>
On 6/5/26 10:51 PM, Tom Tromey wrote:
> Tom> I did wonder whether we should add __attribute__((nonstring)) to
> Tom> gdb_byte, but atm it doesn't seem necessary.
>
> Thinking about this, I wonder if we should change gdb_byte to be a
> uint8_t rather than unsigned char.
>
I suppose there can be type-based alias consequences.
Thanks,
- Tom
prev parent reply other threads:[~2026-06-05 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 19:05 Tom Tromey
2026-06-05 7:38 ` Tom de Vries
2026-06-05 7:41 ` Tom de Vries
2026-06-05 20:51 ` Tom Tromey
2026-06-05 21:13 ` Tom de Vries [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=1e125dd7-c1e2-40c7-9ee4-63cdaa0f93e1@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=tromey@adacore.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