From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] More use of checked_static_cast
Date: Sun, 16 Oct 2022 12:16:16 -0600 [thread overview]
Message-ID: <874jw3eirz.fsf@tromey.com> (raw)
In-Reply-To: <20220925211107.709402-1-tom@tromey.com> (Tom Tromey's message of "Sun, 25 Sep 2022 15:11:05 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> I noticed a few more spots that could use checked_static_cast, and
Tom> this short series is the result.
Tom> Regression tested on x86-64 Fedora 34.
I'm checking this in now.
Tom
prev parent reply other threads:[~2022-10-16 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 21:11 Tom Tromey
2022-09-25 21:11 ` [PATCH 1/2] Use checked_static_cast in more places Tom Tromey
2022-09-25 21:11 ` [PATCH 2/2] More uses of checked_static_cast Tom Tromey
2022-10-16 18:16 ` Tom Tromey [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=874jw3eirz.fsf@tromey.com \
--to=tom@tromey.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).