From: Simon Marchi <simark@simark.ca>
To: Flavio Cruz <flaviocruz@gmail.com>,
bug-hurd@gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Hurd port: update interface to match upstream and fix warnings.
Date: Wed, 7 Feb 2024 11:47:30 -0500 [thread overview]
Message-ID: <3057a492-37bd-450a-8675-26c92d7abd5b@simark.ca> (raw)
In-Reply-To: <ZcMo9FIP35iyiVmA@jupiter.tail36e24.ts.net>
On 2/7/24 01:53, Flavio Cruz wrote:
> We have recently updated the interface for raising exceptions to use
> long [1] and updated mach_port_t to be "unsigned int". This patches fixes
> those problems and will help us port GDB to Hurd x86_64.
>
> Tested on Hurd i686 and x86_64.
>
> [1] https://git.savannah.gnu.org/cgit/hurd/gnumach.git/tree/include/mach/exc.defs
I take it that you are not too concerned with backwards compatibility
with previous versions of Hurd (compiling new GDBs on old Hurds)? If
so, this is fine with me.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
next prev parent reply other threads:[~2024-02-07 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 6:53 Flavio Cruz
2024-02-07 16:47 ` Simon Marchi [this message]
2024-02-07 17:01 ` Samuel Thibault
2024-06-25 14:26 ` Flávio Cruz
2024-06-25 17:05 ` Simon Marchi
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=3057a492-37bd-450a-8675-26c92d7abd5b@simark.ca \
--to=simark@simark.ca \
--cc=bug-hurd@gnu.org \
--cc=flaviocruz@gmail.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