Closed
Bug 686308
Opened 13 years ago
Closed 13 years ago
Warnings in the ARM back-end.
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 686317
People
(Reporter: jbramley, Unassigned)
Details
Attachments
(1 file)
7.46 KB,
patch
|
Details | Diff | Splinter Review |
I get several warnings when building the JS shell on ARM. These aren't new, but I don't think there's a bug for them yet. Specifically: [...]/ARMAssembler.h: In member function ‘void JSC::ARMAssembler::mem_imm_off(bool, bool, int, bool, int, int, JSC::ARMWord, JSC::ARMAssembler::Condition)’: [...]/ARMAssembler.h:591: warning: format ‘%u’ expects type ‘unsigned int’, but argument 9 has type ‘const char*’ [...]/ARMAssembler.h:591: warning: too many arguments for format [...]/ARMAssembler.h: In member function ‘void JSC::ARMAssembler::mem_reg_off(bool, bool, int, bool, int, int, int, JSC::ARMAssembler::Condition)’: [...]/ARMAssembler.h:630: warning: too many arguments for format [...]/ARMAssembler.h: In static member function ‘static void JSC::ARMAssembler::repatchInt32(void*, int32_t)’: [...]/ARMAssembler.h:1056: warning: format ‘%p’ expects type ‘void*’, but argument 4 has type ‘int32_t’ [...]/ARMAssembler.h: In member function ‘void JSC::ARMAssembler::fcpyd_r(int, int, JSC::ARMAssembler::Condition)’: [...]/ARMAssembler.h:1610: warning: too few arguments for format /work/moz/mc/js/src/assembler/assembler/ARMAssembler.h: In member function ‘void JSC::ARMAssembler::fabsd_r(int, int, JSC::ARMAssembler::Condition)’: [...]/ARMAssembler.h:1653: warning: too few arguments for format I think they're mostly related to IPFX, but haven't confirmed that. These should be easy enough to fix.
Reporter | ||
Comment 1•13 years ago
|
||
Attachment #559960 -
Flags: review?(mrosenberg)
Reporter | ||
Comment 2•13 years ago
|
||
Never mind. This was filed separately and fixed elsewhere.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•13 years ago
|
Attachment #559960 -
Flags: review?(mrosenberg)
You need to log in
before you can comment on or make changes to this bug.
Description
•