[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 64bit GNU Mach
From: |
Richard Braun |
Subject: |
Re: 64bit GNU Mach |
Date: |
Mon, 2 Apr 2012 14:58:55 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Mon, Apr 02, 2012 at 02:54:17PM +0200, Samuel Thibault wrote:
> > I believe we're thinking of two different things here. My current idea
> > of the solution is to directly convert names (32-bits) to ports or other
> > IPC objects (e.g. port sets, 64-bits).
>
> That's what I'm suggesting from the beginning. That needs two differents
> types (64bit mach_port_t and 32bit mach_port_name_t), where there is
> currently just one (vm_offset_t mach_port_t).
Then I don't see why you want two different types. There would be one
32-bits mach_port_t, and no mach_port_name_t.
--
Richard Braun
- Re: 64bit GNU Mach, (continued)
- Re: 64bit GNU Mach, Richard Braun, 2012/04/02
- Re: 64bit GNU Mach, Samuel Thibault, 2012/04/02
- Re: 64bit GNU Mach, Richard Braun, 2012/04/02
- Re: 64bit GNU Mach, Samuel Thibault, 2012/04/02
- Re: 64bit GNU Mach, Richard Braun, 2012/04/02
- Re: 64bit GNU Mach, Samuel Thibault, 2012/04/02
- Re: 64bit GNU Mach, Richard Braun, 2012/04/02
- Re: 64bit GNU Mach, Samuel Thibault, 2012/04/02
- Re: 64bit GNU Mach, Richard Braun, 2012/04/02
- Re: 64bit GNU Mach, Samuel Thibault, 2012/04/02
- Re: 64bit GNU Mach,
Richard Braun <=
- Re: 64bit GNU Mach, Samuel Thibault, 2012/04/02
- Re: 64bit GNU Mach, Richard Braun, 2012/04/02
Re: 64bit GNU Mach, Roland McGrath, 2012/04/02