From: "Flávio Cruz" <flaviocruz@gmail.com>
To: Simon Marchi <simark@simark.ca>,
bug-hurd@gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Hurd port: update interface to match upstream and fix warnings.
Date: Tue, 25 Jun 2024 15:26:45 +0100 [thread overview]
Message-ID: <CAKwpGPzzM-z4OWhV=S51dxMkFbZcOuBcTRSCzSZJYEEbK1POdw@mail.gmail.com> (raw)
In-Reply-To: <20240207170130.rffgkvqqtkgnjxaa@begin>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Hi Simon
On Wed, Feb 7, 2024 at 5:01 PM Samuel Thibault <samuel.thibault@gnu.org>
wrote:
> Simon Marchi, le mer. 07 févr. 2024 11:47:30 -0500, a ecrit:
> > 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)?
>
> We don't have any other 64bit version of the Hurd, and for the 32bit
> version this is a no-op.
>
> > If so, this is fine with me.
> >
> > Approved-By: Simon Marchi <simon.marchi@efficios.com>
>
Anything else we need to do to merge this patch?
Thank you
>
> Thanks!
>
> Samuel
>
[-- Attachment #2: Type: text/html, Size: 1825 bytes --]
next prev parent reply other threads:[~2024-06-25 14:27 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
2024-02-07 17:01 ` Samuel Thibault
2024-06-25 14:26 ` Flávio Cruz [this message]
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='CAKwpGPzzM-z4OWhV=S51dxMkFbZcOuBcTRSCzSZJYEEbK1POdw@mail.gmail.com' \
--to=flaviocruz@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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