Status

()

defect
RESOLVED INVALID
9 years ago
8 years ago

People

(Reporter: glandium, Assigned: glandium)

Tracking

Trunk
Sun
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: not-ready)

Attachments

(1 attachment)

Assignee

Description

9 years ago
The configure check activates JIT on sparc*, but only defines AVMPLUS_SPARC on sparc. In sparc64 case, this leads to a failure to build, because it falls on
#error "unknown nanojit architecture".
Assignee

Comment 1

9 years ago
Assignee: general → mh+mozilla
Attachment #468275 - Flags: review?(benjamin)

Updated

9 years ago
Attachment #468275 - Flags: review?(benjamin) → review+
Assignee

Updated

9 years ago
Attachment #468275 - Flags: approval2.0?

Updated

9 years ago
Attachment #468275 - Flags: approval2.0? → approval2.0+
Assignee

Comment 2

9 years ago
I'm starting to wonder. As far as my testing goes, nanojit works on sparc64. But I'm wondering if there shouldn't be a AC_DEFINE(AVMPLUS_64BIT) somewhere, in which case nanojit sparc doesn't have the necessary functions, e.g. asm_qbinop
Comment on attachment 468275 [details] [diff] [review]
Define AVMPLUS_SPARC for sparc*

Sorry, too late for 2.0.
Attachment #468275 - Flags: approval2.0+ → approval2.0-
Assignee

Comment 4

8 years ago
I have doubts anyway, cf. comment 2.
This can land in the build-system branch (if you actually want it).
Whiteboard: not-ready
Assignee

Comment 6

8 years ago
Let's mark it invalid, this predates the new jsvalue and since then sparc64 can't work properly. There is at least one bug for the js engine to work on sparc64.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.