did you provide additional flags to
configure.py ? and if so, which ones?
under “Building Tamarin for Android 2.3.3 on Mac”
you can see
$ hg clone http://hg.mozilla.org/tamarin-redux
$ cd tamarin-redux
$ mkdir objdir-release
$ cd objdir-release
$ ../configure.py --arm-arch=armv7-a --target=arm-android
did you use something like that?
configure.py --arm-arch=armv7-a --target=arm-android ?
you can also run
$ configure.py --help
to view all the different flags avaiable
build/avmfeatures.py to see how some contant features equals to command-line params
core/avmfeatures.as to get the details of the feature
The reason it won't work is that some compilers (notably on ARM) will generate
code that uses a floating-point load into an FP register, so the code actually
needs unaligned floating-point loads to be supported, AVMSYSTEM_UNALIGNED_FP_ACCESS.
(Whether it is correct for the compiler to generate that code is beside the point.)
The prohibition applies to 64-bit loads/stores as well (expressed as pairs of
uint32_t loads/stores): ARM compilers as of October 2011 will rewrite a pair of loads
into a uint32_t array in a union with a return of a double from the union as a single
double load into the return register. See comments throughout the code as well
as Bugzilla 569691 and 685441.