• Moderator
    Posts: 461 from 2003/7/21

    Yasu wrote:
    I don't want to burden Bigfoot with more work, but are you capable of fixing the OWB javascriptcore big endian issue? I understand if you don't have time or if the job is too big, but would you be able to do it if someone put a gun to your head? :-)

    Uhm, if you actually read carefully bigfoot post, you would see that it is basically what he is dealing with.

    bigfoot wrote:
    The JIT engine then generates code that expects the upper 32 bits of the 64 bit floating point value to be located at address + 4.

    This means that the JIT engine addresses the values using the little endian format. On the contrary, for big endian CPUs (like the PPC) the upper 32 bits are located at address and the lower 32 bits at address + 4. When bigfoot is done, we would have a working javascript again, and a JIT one at it... And I am confident that bigfoot is also making sure that either this engine can be merged with upstream WebKit or that at least synch with updated upstream WebKit releases can be performed.

    Mark is of course free to correct me where I am wrong.

    Kind regards,
  • »14.01.16 - 22:12