Code: Select all
┌───────────────────────────────────────────────────────────────────────────┐ >│0x57232028 movw r1, #56900 ; 0xde44 │ │0x5723202c movt r1, #10989 ; 0x2aed │ │0x57232030 ldr r12, [pc, #624] ; 0x572322a8 │ │0x57232034 blx r12 │ │[…] │ └───────────────────────────────────────────────────────────────────────────┘
Unfortunately, there was no response.[02:15:28] <Hexxeh> getting illegal instruction on pages with JS, is there anywhere that v8 needs to be separately configured for armv6, not armv7?
[02:35:35] <Hexxeh> looks like movw sneaking it's way in somehow
Code: Select all
ifeq (armhf,$(DEB_HOST_ARCH)) GYP_DEFINES += -DUSE_EABI_HARDFLOAT GYP_DEFINES += \ v8_use_arm_eabi_hardfloat=true \ v8_can_use_vfp2_instructions=true \ arm_fpu=vfp \ arm_float_abi=hard \ arm_thumb=0 \ armv7=0 \ arm_neon=0 \ $(NULL) endif
if it was due to soft FP, wouldn't it also run slowly on the Squeeze distort? it doesn't.centerorbit wrote:@jui-feng: Would you guess that chromium runs incredibly slow due to high use of software-floating point? Would you expect it to run much faster on raspbian?
I think that my chromium build was already using hardware floating point, so it's probably not due to software floating point.centerorbit wrote:@jui-feng: Would you guess that chromium runs incredibly slow due to high use of software-floating point? Would you expect it to run much faster on raspbian?
The version in squeeze was truly ancient. It's very possible (likely even) that architectural changes in chromium mean that performance is currently poor on the Raspberry Pi.marsman2020 wrote:The last version of Chromium I was able to test on the Pi was the version that is in the squeeze repo pointed to by the original 4-19-2012 Debian Squeeze image.
It seemed a tad faster then Midori, so I don't really understand the slowness that you are seeing.
I got your patch and it looks sane, I had some minor issues getting it into the repo (not your fault just little annoyances like a source package that can't do an indep-only build so I had to do a full build on amd64 to get the indep packages built), the source and architecture independent packages are now in the repo and build00 has started building the architecture dependent packages.jui-feng wrote: Anyway, I've sent plugwash a link to the source package so he may review my changes. If he finds the time, is satisfied with my patch, and there is some spare build capacity on the raspbian build servers, you might see the chromium-browser package appear in the raspbian repo, so you can check the slowness out for yourself.
This is probably an incredibly stupid question but why can't it be built using that version?asb wrote:
The version in squeeze was truly ancient. It's very possible (likely even) that architectural changes in chromium mean that performance is currently poor on the Raspberry Pi.