Hello, All -
I guess it's time to publicly 'fess up to being someone who is
working on porting wine to PPC. I'm still a relative wine newbie, but I
welcome interested parties to contact me about wine ports if they'd like
as I will be working on it regularly for some time.
My first question to the group is: does anyone know of a good place
to put the TEB thread-info structures on the PPC architecture? On Intel
they get stored in the fs register, and on non-intel sparc there's some
thread-local storage pointer the OS gives you. It _looks_ like
linuxthreads for PPC puts all its thread info in a big list, so that's
what I've done (in a hacky way) for linuxppc. I feel like it should
change eventually, though (I'm just shooting for something that works
for the time being) because finding the current thread means getting a
pointer you think is on the stack and then searching the whole list for
a TEB with a stack that could contain that pointer. Seems slow.
Does anyone know of a really _good_ place to put these on the PPC?
Looking at a ppc manual I see some general purpose registers -
spg0-spg3 that are reserved for OS use, but I assume there's no way for
a user-level program to set them under linux?
Thanks!
Josh.
>
> Michael Cohen wrote:
> >
> > Guys,
> >
> > I've been pondering this one for a while now. If endianness is
> > accounted for, can WINE be ported to different architectures / operating
> > systems?
>
> Winelib (the Windows implementation and porting library) has been
> ported to PPC once by Gavriel State, and has been again by Josh Dubois
> of CodeWeavers [okay, Josh only has it sorta kinda working, but there
> you go].
> There is still a fair amount of work to do to get the non intel Winelib
> working well, but it's only that - work - nothing really hard left <g>.
>
--
Josh DuBois
654 SW Grant #103, Portland, OR 97201
503-827-4818
[EMAIL PROTECTED]
