summaryrefslogtreecommitdiff
path: root/faq/64-bit.mdwn
blob: d3d6d046c48a99b727596870bd0c44f35121a238 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
[[!meta copyright="Copyright © 2013, 2016, 2017, 2018 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
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag faq/support]]

[[!meta title="Is there a 64-bit version?"]]

64-bit kernelland is supported with 32-bit userland, which notably
permits to efficiently make use of more than 2 GiB memory and provide 4 GiB
userland addressing space.

A 64-bit GNU/Hurd is also available, progress is tracked on [[open_issues/64-bit_port]]!
As of April 2025, the Debian hurd-amd64 port works just like the hurd-i386, except for
some bugs, namely swapping issues with rumpdisk and dumping core files.

We plan on supporting both a 
32-bit and 64-bit Debian GNU/Hurd, only not both at the same time.  
However, there is no plan to fix the year 2038 concern on a 32-bit system.

That being said, you can always run a 32-bit version on a 64-bit machine, it
just works, processes are just limited to a couple GiB available memory.