8 years ago
Last year


(Reporter: m_kato, Assigned: m_kato, NeedInfo)


(Depends on 1 bug)

Windows 8
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)


Windows 8 and VS11 support arm target, I would like to add arm target for experiment.
Depends on: 687033
Interesting. Is this different from Windows CE?
(In reply to Ted Mielczarek [:ted, :luser] from comment #1)
> Interesting. Is this different from Windows CE?

This is presumably to support Windows 8 on ARM devices. This will require MSVC 2011 support, so adding that as a blocker.
Depends on: 686837
(In reply to Ted Mielczarek [:ted, :luser] from comment #1)
> Interesting. Is this different from Windows CE?

- ABI seems to be different.  double must be 8 bytes alignment.
- ARMv7 + thumb2 by default.  No option to use ARMv6
Blocks: VC11
Depends on: 712841
No longer depends on: 712841
MS is only allowing Metro apps on ARM at this point so I'm marking this as invalid.
Closed: 7 years ago
Resolution: --- → INVALID
Maybe it's time to reconsider this for Windows 10 since it's launching to device like Raspberry Pi 2 ?
It depends on whether Microsoft has changed their stance on the issue raised in comment 4.
Duplicate of this bug: 1439202
Please support "Wine for Android"(compatibility layer) in AMR device.
Flags: needinfo?(netzen)
Windows 10 on ARM?
Flags: needinfo?(m_kato)
(In reply to In from comment #9)
> Windows 10 on ARM?

If we start to develop it, we (I?) will create meta bug for our work items.  So I don't know current plan and we shouldn't reopen this at this time.

Also, When WinRT age, I had a lot of patch set for jailbreak'ed WinRT...
Flags: needinfo?(m_kato)
And as long as I know, Microsoft is testing for Firefox on WoA on x86 emulation.  And even if we port Firefox to aarch64, we don't have IonJIT compiler for aarch64, so Firefox x86 will faster than Firefox aarch64.
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.