From 9933cec0a18ae2a3d752f269d1bb12c19f51199d Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 21 Jul 2013 15:35:02 -0400 Subject: IRC. --- open_issues/64-bit_port.mdwn | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) (limited to 'open_issues/64-bit_port.mdwn') diff --git a/open_issues/64-bit_port.mdwn b/open_issues/64-bit_port.mdwn index 66da44b9..b0c95612 100644 --- a/open_issues/64-bit_port.mdwn +++ b/open_issues/64-bit_port.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2011, 2012 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2011, 2012, 2013 Free Software Foundation, +Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -137,3 +138,20 @@ See also [[microkernel/mach/gnumach/memory_management]]. hm actually no, it would require mcmodel=large hum, that's stupid, we can make the kernel run at -2g, and use 3g up to the sign extension hole for the kernel map + + +# IRC, freenode, #hurd, 2013-07-02 + +In context of [[mondriaan_memory_protection]]. + + BTW, it's not like I have an infinite amount of time for this, + but having 64-bit support would be valuable for me, so I might contribute + that back if it's not a too monumental task + I saw some discussions about 32bit apps on top of 64bit mach, but + I'd like a full 64bit system + any clues? + I suppose the compiler support is all there already + is MIG (and mach) the only piece missing? + the problem is the interfaces themselves + type widths + as passed between userspace and kernel -- cgit v1.2.3