[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#637424: Implement i386_get_gsbase i386_get_fsbase i386_set_gsbase i386_set_fsbase amd64_get_gsbase amd64_get_fsbase amd64_set_gsbase amd64_set_fsbase



On Tue, Aug 16, 2011 at 06:36:08PM +0200, Robert Millan wrote:
> 2011/8/11 Robert Millan <rmh@debian.org>:
> > 2011/8/11 Aurelien Jarno <aurelien@aurel32.net>:
> >> In any case, they will have to wait for 2.14. Anyway, what are the uses
> >> cases for these?
> >
> > wine needs amd64_set_gsbase and i386_set_fsbase.
> 
> Here's a new patch which only implements the syscall stubs needed by
> wine (amd64_set_gsbase and i386_set_fsbase).
> 
> This patch also corrects a critical mistake: in setters, the pointers
> are passed by reference just like with getters (this confusion led me
> to report non-bug #637528, more details there).
> 

This new patch still doesn't answer my question: why wine can't use
the sysarch interface for that?

I am really worried by so much requests of adding BSD specific
functions. If we want all the FreeBSD libc functions, why don't we use the
FreeBSD libc instead of the GNU libc?

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net



Reply to: