Re: [Sbcl-devel] What is the scope of SBCL porting on Windows 7 x86-64?

[Roman M. <rom...@gm...>]

Also, Win64 LLP64 data model assumes C 'long' type to be still 32 bits long,
while on Linux LP64 assumes 'long' to be 64 bits long. Such cases should be
taken into account and fixed in src/runtime (if any).

2010/7/13 Kalyanov Dmitry <kal...@gm...>

> On Tuesday 13 July 2010 21:15:39, Roman Marynchak wrote:
> > Hello All,
> >
> >  I use SBCL at work, but our product migrates on Windows 7 x64 and
> requires
> > the appropriate 64-bit CL implementation (capable of using 4+ GB of
> memory,
> > emitting AMD64 code and so on). So, I wonder how long it can take to port
> > SBCL there?
> >
> > Actually, there are three specific questions:
> >
> > 2. What are the technical problems connected with this port?
>
> As far as I know, the main difference between Win64 and Win32 is different
> exception handling mechanism. In Win32, functions pushed and popped SEH
> frames; in Win64 exception handling is table-based: each function is
> associated with exception information table; it's documented in
> http://msdn.microsoft.com/en-us/library/7kcdt6fy%28v=VS.80%29.aspx). Win64
> differs from other x86-64 OSes in calling convention.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Sbcl-devel mailing list
> Sbc...@li...
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel
>
>