667842 - Unable to compile a js shell on Pegatron ARM box

Status: RESOLVED INCOMPLETE

(Core :: JavaScript Engine, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

I'm no longer able to compile a js shell on a ARM pegatron box, since TM changeset 4e334541e521 and possibly going back till 48489a602029 or even prior.

The gcc version is 4.3.3.

Compilation still works on a Tegra 2 Ubuntu though.

Is this intended?

===

jsgcstats.cpp
jshash.cpp
jsinterp.cpp
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

In the directory  /mnt/nth10sd/Desktop/jsfunfuzz-dbg-32-tm-71605-5b5cdbaaccd5/compilePath/js/src/opt-objdir
The following command failed to execute properly:
/opt/cs2007q3/bin/g++ -o jsinterp.o -c -fvisibility=hidden -DOSTYPE="Linux2.6" -DOSARCH=Linux -DEXPORT_JS_API -DIMPL_MFBT -D__STDC_LIMIT_MACROS -I/mnt/nth10sd/Desktop/jsfunfuzz-dbg-32-tm-71605-5b5cdbaaccd5/compilePath/js/src -I. -I./dist/include -I./dist/include/nsprpub -I/mnt/nth10sd/Desktop/jsfunfuzz-dbg-32-tm-71605-5b5cdbaaccd5/compilePath/js/src -I/mnt/nth10sd/Desktop/jsfunfuzz-dbg-32-tm-71605-5b5cdbaaccd5/compilePath/js/src/assembler -I/mnt/nth10sd/Desktop/jsfunfuzz-dbg-32-tm-71605-5b5cdbaaccd5/compilePath/js/src/yarr -fPIC -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -pedantic -Wno-long-long -fno-strict-aliasing -pthread -pipe -DNDEBUG -DTRIMMED -g -O3 -fstrict-aliasing -fno-stack-protector -fno-omit-frame-pointer -DUSE_SYSTEM_MALLOC=1 -DENABLE_ASSEMBLER=1 -DENABLE_JIT=1 -DMOZILLA_CLIENT -include ./js-confdefs.h -MD -MF .deps/jsinterp.pp /mnt/nth10sd/Desktop/jsfunfuzz-dbg-32-tm-71605-5b5cdbaaccd5/compilePath/js/src/jsinterp.cpp
make[1]: *** [jsinterp.o] Error 1
make[1]: *** Deleting file `jsinterp.o'
make: *** [default] Error 2

Comment 1

[David Mandelin [:dmandelin]]

(In reply to comment #0)
> I'm no longer able to compile a js shell on a ARM pegatron box, since TM
> changeset 4e334541e521 and possibly going back till 48489a602029 or even
> prior.
> 
> Is this intended?

Stuart, how important is it to have shells building on Pegatrons? I assume we are pretty much going to Tegras for our testing/development. But do we still have contributors with Pegatrons, etc?

Comment 2

[Jesse Ruderman]

I believe Gary is using the Pegatron box on my desk.  Should we request a Tegra or try to keep the Pegatron alive?

Comment 3

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

(In reply to comment #2)
> I believe Gary is using the Pegatron box on my desk.  Should we request a
> Tegra or try to keep the Pegatron alive?

Well, we have a Tegra for fuzzing, just not at the MV office. ;-)

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Stuart, re-ping? Else the Pegatron is just sitting idle and drinking electricity without any productivity..

Comment 5

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

The Pegatron box has gone to the big rack in the sky, aka back to IT.

-> INCOMPLETE