Open Bug 720214 Opened 14 years ago Updated 3 years ago

Can --disable-neon please be added?

Categories

(Firefox Build System :: General, defect)

All
Linux
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: joop.boonen, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 2011122000 Steps to reproduce: As NEON (ARM extension) currently doesn't build on openSUSE and to be able to disable the optional NEON module. I would like to have --disable-neon to be added. I've attached a patch. This is the case for Firefox and Thunderbird and maybe other programs.
The patch I've attached might not meet your standard. Can It please be adapted to your standard, if this this optional configure argument is accepted?
Component: General → Build Config
QA Contact: general → build-config
Hardware: x86_64 → All
Confirm request. On tegra2-based sysems(armv7, wo neon and simd) thise optimizations brake final linking
tryed 10.0esr, --disable-neon still dont work. with neon we must disable simd and armv6 optimizations on armv7-a systems
(In reply to Joop Boonen from comment #0) > As NEON (ARM extension) currently doesn't build on openSUSE and to be able > to disable the optional NEON module. I would like to have --disable-neon to > be added. I'm just curious about how this build problem looks. Isn't NEON supposed to be buildable with any non-ancient gcc compiler and properly runtime detected when run on ARM devices?
(In reply to macau from comment #3) > we must disable simd and armv6 optimizations on armv7-a systems why disabling armv6 optimizations on tegra2?
Is there still interest in getting this patch into the tree? Then this bug should be moved forward in some way..
Product: Core → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: