Re: [libposix-development] Some restructuring, preliminary (non-functional) x86-64 port

[Henrique A. <hd...@gm...>]

 BTW, I hope to install Ubuntu amd64 here this week, so I'll be able
to help with the port.

2009/6/2 Henrique Almeida <hd...@gm...>:
> 2009/6/2 Andreas Krennmair <akr...@go...>:
>> On Tue, Jun 2, 2009 at 3:55 PM, Andreas Krennmair
>>
>> This patch is obsolete, here's the new patch set containing both the old
>> patch and some amendments to it that make it work on x86_64:
>> http://synflood.at/tmp/libposix/x86_64-working.mbox
>
>  Nice. Many comments, though:
>
> - x86_64 also seems to use vsyscall, as shown by the virtual library
> "vdso" shown by Tordek output (ldd /bin/ls) on the other post. Is it
> safe to use "syscall" directly ? I need a valid reference for the
> system call specification on x86_64.
> - _start.S: is the third parameter (envp) correct ? It needs to point
> to the first environment variable. Isn't the correct address
> rsi+8*rdi+16 ?
>  - syscall_nums.h: It seems that you've copied and pasted those. That
> can't be done. The original license and author must be present in the
> source. Also, that license needs to be BSD (the project will have a
> single license, I'll talk about this). Also, is this from a GPL libc ?
> We can't refer to GPL competitors, else our library will become a
> "derivative work" and we'll need to relicense it as GPL.
>  - syscalls.S: are you sure you don't need to save the register values
> for the caller ? Would the code compiled, say, as -O3 (with the
> compiler inlining functions and aggressively using registers) always
> work ? Again, I need a valid reference for the calling conventions
> specification on x86_64
>
>  I have setup a branch for your patches in my local repository, so you
> can have some time to answer the questions.
>
>>
>> Please note that this not only switches from nasm to GNU as but also breaks
>> current x86 support as I don't have a proper development machine to test any
>> changes to x86. But changes to get x86 running again should be trivial.
>
>  Yes, x86 compilation is broken. :-/
>
>>
>> So, in short: libposix has gone multiplatform!
>
>  Cool ! :-D The next step is port to a non linux platform. David said
> he had easy access to NetBSD and Mac OS X. David, do you think you can
> help with the port for those ?
>
>  Anyway, before we continue with the ports, it's a good idea to switch
> to a "next generation" build system and define how "platform set"
> configuration files will behave.
>
>>
>> Regards,
>> Andreas
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...