2013/9/11 Mike Hommey <m...@glandium.org> > On Wed, Sep 11, 2013 at 04:39:37PM -0700, jmaher wrote: > > quite possibly we don't need all those jobs running on tegras. I > > don't know of a bug in the product that has broken on either the tegra > > or panda platform but not the other. > > Off the top of my head: > > - I have broken one but not the other on several occasions, involving > differences in the handling of instruction and data caches, but unless > you're touching the linker or the jit, it shouldn't matter. > > - Tegras don't have neon instructions, so wrong build flags, or wrong run > time detection could trigger failures on one end and not the other. > > - GPUs on tegras and pandas, as well as their supporting libraries, > differ, too. But unless you are touching graphics code, that shouldn't > matter, unless your changes trigger some pre-existing bug.. >
And Panda boards have 1G of RAM, which is more than the Tegra boards have, right? Surely that can help avoiding OOM problems on Pandas. At some point earlier this year, WebGL conformance tests were perma-orange on Tegras but only intermittently orange on Pandas. RAM differences were likely the cause, as WebGL tests were OOM'ing a lot. Benoit > > So, while chances of breaking one and not the other are slim, they do > exist. > > Mike > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
