Closed
Bug 667130
Opened 14 years ago
Closed 14 years ago
SIMD/THUMB2 detections fail under Android NDK5
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla7
People
(Reporter: jchen, Assigned: blassey)
Details
(Keywords: mobile, perf)
Attachments
(2 files, 1 obsolete file)
1.76 KB,
text/plain
|
Details | |
826 bytes,
patch
|
glandium
:
review+
|
Details | Diff | Splinter Review |
1) HAVE_ARM_SIMD and HAVE_ARM_THUMB2 are not detected in configure because we detect them based on target, and for NDK5 we are using a different target in mozconfig
2) When building with -fno-omit-frame-pointer, "gfx/ycbcr/yuv_convert_arm.cpp" and "toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.cc" fail for using the frame pointer register. "exception_handler.cc" has protection for this (see toolkit/crashreporter/google-breakpad/src/client/linux/handler/Makefile.in) but it didn't work for me when I try something like 'ac_add_options --enable-optimize="-fno-omit-frame-pointer"'
Attached is the WIP patch I used to fix the -fno-omit-frame-pointer bug
Comment 1•14 years ago
|
||
Some questions:
Did you see any problem with 1), or just notice it?
Is issue 2) new with NDK5, or existing with NDK4 as well?
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
> Some questions:
>
> Did you see any problem with 1), or just notice it?
In the very least, this causes us to not build pixman-arm-simd.c and pixman-arm-simd-asm.S.
> Is issue 2) new with NDK5, or existing with NDK4 as well?
this is only a problem with NDK5
Comment 3•14 years ago
|
||
Issue 2 is a dupe of bug 666918.
Updated•14 years ago
|
Comment 4•14 years ago
|
||
(In reply to comment #2)
> (In reply to comment #1)
> > Is issue 2) new with NDK5, or existing with NDK4 as well?
> this is only a problem with NDK5
I think issue 2 will turn up in NDK5 once issue 1 is fixed. The error is thrown from a NEON routine, so I assume that it's just not being compiled under NDK5, since it thinks it doesn't have NEON.
I've attached a fix for issue 2 to bug 666918.
Comment 5•14 years ago
|
||
Let's refocus this bug on the SIMD/Thumb2 detection failure in NDK5.
Summary: SIMD/THUMB2 detections and no-omit-frame-pointer flag fail under Android NDK5 → SIMD/THUMB2 detections fail under Android NDK5
Assignee | ||
Comment 6•14 years ago
|
||
Assignee: nobody → blassey.bugs
Attachment #542899 -
Flags: review?(khuey)
Comment 7•14 years ago
|
||
Comment on attachment 542899 [details] [diff] [review]
patch to fix simd/thumb2 detection
Review of attachment 542899 [details] [diff] [review]:
-----------------------------------------------------------------
::: configure.in
@@ +6959,4 @@
>
> dnl Defaults
> case "${target}" in
> + *-android*|*-linuxandroid*)
You could use *-*android*) ... but why remove arm?
Assignee | ||
Comment 8•14 years ago
|
||
(In reply to comment #7)
> Comment on attachment 542899 [details] [diff] [review] [review]
> You could use *-*android*) ...
yup, but in previous patches/reviews we decided to be more prescriptive
> but why remove arm?
probably shouldn't
Assignee | ||
Comment 9•14 years ago
|
||
Attachment #542899 -
Attachment is obsolete: true
Attachment #542906 -
Flags: review?(khuey)
Attachment #542899 -
Flags: review?(khuey)
Comment 10•14 years ago
|
||
Comment on attachment 542906 [details] [diff] [review]
patch to fix simd/thumb2 detection
Review of attachment 542906 [details] [diff] [review]:
-----------------------------------------------------------------
::: configure.in
@@ +6959,4 @@
>
> dnl Defaults
> case "${target}" in
> + arm-android*|arm-linuxandroid*)
r=me with that heading space removed.
Attachment #542906 -
Flags: review?(khuey) → review+
Assignee | ||
Comment 11•14 years ago
|
||
pushed to inbound (m-c is pretty colors right now) http://hg.mozilla.org/integration/mozilla-inbound/rev/1b9de1c16455
Comment 12•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla7
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•