Summary: | webkitgtk 2.3.92 fails to build on Debian/armhf: error: unable to find a register to spill in class 'LO_REGS' | ||
---|---|---|---|
Product: | WebKit | Reporter: | Iain Lane <iain.lane> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | berto, gustavo, zan |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Linux |
Description
Iain Lane
2014-03-20 06:15:29 PDT
I saw this but I didn't have the time to look into it yet, thanks for reporting! I spoke to the GCC maintainer in Debian & Ubuntu and he believes it's a bug in gcc-4.8 that webkit exposed by adding -fno-tree-dce in .92. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60617 (In reply to comment #2) > I spoke to the GCC maintainer in Debian & Ubuntu and he believes > it's a bug in gcc-4.8 that webkit exposed by adding -fno-tree-dce in > .92. > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60617 I'm not sure why we need -fno-tree-dce anyway. Žan? (In reply to comment #3) > (In reply to comment #2) > > I spoke to the GCC maintainer in Debian & Ubuntu and he believes > > it's a bug in gcc-4.8 that webkit exposed by adding -fno-tree-dce in > > .92. > > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60617 > > I'm not sure why we need -fno-tree-dce anyway. Žan? This avoids an apparent GCC 4.8 bug which was crashing tests after the jsCStack branch was merged. The optimization was disabled in bug #127909. Still failing as of 2.4.0 How many JSC tests fail on the armhf build if the -fno-tree-dce flag is removed? (In reply to comment #6) > How many JSC tests fail on the armhf build if the -fno-tree-dce flag is removed? I cannot give it a try right now but I'll try to do it as soon as I have the time. The armhf machine I'm trying on is very slow, but at least JSC seems to build fine. I'd say let's disable -fno-tree-dce in Debian for the time being until the GCC bug is solved. |