Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross compile V7 and failed to run on mips-32bit #547

Open
ghost opened this issue Mar 12, 2016 · 9 comments
Open

Cross compile V7 and failed to run on mips-32bit #547

ghost opened this issue Mar 12, 2016 · 9 comments
Assignees

Comments

@ghost
Copy link

ghost commented Mar 12, 2016

./v7: v7.c: 9223: calc_llen: Assertion `n <= (int) sizeof(len)' failed.
Aborted

@goniz
Copy link

goniz commented Jun 8, 2016

I'm experiencing this problem as well.
Can a fix be implemented easily?

@mkmik
Copy link
Collaborator

mkmik commented Jun 8, 2016

big endian?

@goniz
Copy link

goniz commented Jun 9, 2016

Yes, big endian.

On Thu, Jun 9, 2016, 00:52 Marko Mikulicic notifications@github.com wrote:

big endian?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#547 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AA7no7Zn2bXs3WFLUI21R5G_Bn3qvVzGks5qJzmpgaJpZM4HvLja
.

@goniz
Copy link

goniz commented Jun 9, 2016

Is this a 32bit vs 64bit issue? or a big endian vs little endian issue?

@dimonomid
Copy link
Contributor

v7 runs perfectly fine on both 64bit and 32bit. This is a big-endian issue.

@goniz
Copy link

goniz commented Jun 10, 2016

running ./v7_mips -e 'print(1);' after commit 9111813 give the following output:

"cannot find exception TypeError
Exception creation throws an exception TypeError: cannot read property 'prototype' of undefined
Assertion failed: v7_is_object(v) (v7.c: get_object_struct: 17840)"

@dimonomid
Copy link
Contributor

dimonomid commented Jun 10, 2016

Yes, we're aware of the issues on big-endian platforms; honestly we never addressed them yet. But yes, this thing is important, and we plan to fix it in July 2016 (can't do that earlier due to our local deadlines). We'll report here once we have any progress on that.

@goniz
Copy link

goniz commented Jun 10, 2016

Thank you for the quick response, July sounds great!
I will be following your progress 👍

@goniz
Copy link

goniz commented Jul 2, 2016

Looking forward for the fix :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants