[PATCH gnumach] Remove a.out support for ddb

We haven't built gnumach using a.out for a very long time. --- Makefrag.am | 2 - ddb/db_aout.c | 505 ddb/db_aout.h | 52 - ddb/db_sym.c| 8 +- ddb/db_sym.h| 8 +- i386/i386at/model_dep.c

[PATCH gnumach] memory_object_create_proxy: avoid casting parameters to 32 bits since the types are correct now

--- vm/memory_object_proxy.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/vm/memory_object_proxy.c b/vm/memory_object_proxy.c index 0f1e75e5..57243497 100644 --- a/vm/memory_object_proxy.c +++ b/vm/memory_object_proxy.c @@ -155,13 +155,6 @@ memory_object_create_proxy (ipc_space_t spac

Re: [PATCH] vm_page.c: add missing object lock

Applied, thanks! Etienne Brateau, le mer. 08 févr. 2023 23:54:36 +0100, a ecrit: > The documentation of vm_page_insert says that the object must be locked. > Moreover, the unlock call is here but no call was present. > --- > vm/vm_page.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/v

[PATCH] vm_page.c: add missing object lock

The documentation of vm_page_insert says that the object must be locked. Moreover, the unlock call is here but no call was present. --- vm/vm_page.c | 1 + 1 file changed, 1 insertion(+) diff --git a/vm/vm_page.c b/vm/vm_page.c index 707be4bb..50916b74 100644 --- a/vm/vm_page.c +++ b/vm/vm_page.c

[sr #110199] Cross-building of GNU/Hurd and additional packages

Follow-up Comment #33, sr #110199 (project administration): Hello, this issue seems to have a Closed status. Can somebody open it again? Thanks! ___ Reply to this item at: ___

Re: On SO_PEERCRED & SCM_CREDS

Forgot to mention another interesting possibility: clearly, the auth_{user,server}_authenticate () API has been designed with io_reauth in mind. The newport being passed from the server to the client fits the io_reauth model very well, the newport being a newly authenticated port to the same perop

Re: [gnu-soc] GNU GSOC 2023 application

On Wed, Feb 8, 2023 at 2:45 PM Samuel Thibault wrote: > Actually, no: the rustc compiler itself cross-builds fine, it's libstd > that needs porting, and the gcc front-end uses the rustc libstd too. Is planning to use the upstream libstd, rather. Currently GCC Rust cannot even build libcore yet.

Re: [gnu-soc] GNU GSOC 2023 application

> Jose E. Marchesi, le mer. 08 févr. 2023 12:15:31 +0100, a ecrit: >> As a side note, have you heard of the GCC Rust front-end (under >> development) that has been recently added to GCC? > > Yes. > >> It may be relevant to the Hurd. > > Actually, no: the rustc compiler itself cross-builds fine, i

Re: [gnu-soc] GNU GSOC 2023 application

Jose E. Marchesi, le mer. 08 févr. 2023 12:15:31 +0100, a ecrit: > As a side note, have you heard of the GCC Rust front-end (under > development) that has been recently added to GCC? Yes. > It may be relevant to the Hurd. Actually, no: the rustc compiler itself cross-builds fine, it's libstd tha

Re: [gnu-soc] GNU GSOC 2023 application

Hi Samuel. I added the Hurd idea to the page. Thank you very much. As a side note, have you heard of the GCC Rust front-end (under development) that has been recently added to GCC? It may be relevant to the Hurd. > Hello Jose, > > - GNU Hurd > - The GNU Hurd is the GNU project's replacement