Miscompare of 254.gap in SPEC's cpu000 using 2014.05 Aarch64 release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro GCC |
Invalid
|
Undecided
|
Kugan Vivekanandarajah |
Bug Description
I have been building SPEC's cpu200 suite using the 2014.05 aarch64 release. The benchmark call 254.gap fails to correctly run ( fails to compare in SPEC nomenclature ) using the following flags
* COMP: /opt/gcc-
LINK: /opt/gcc-
* COMP: /opt/gcc-
LINK: /opt/gcc-
However it does generate a correct answer once it drops to -O1 and -O0
Normally I would assume the -O3 was too aggressive but this built at -O3 level and ran with no problems in the 2014.04 release of the Aarch64 compiler. So this is a regression from your previous release.
Changed in gcc-linaro: | |
assignee: | nobody → Kugan Vivekanandarajah (kugan-vivekanandarajah) |
I have started running with arm gnueabihf 2014.05 version and get the same failiure in 254.gap at the -o3 level. I will work the -O flag back once everything else completes.
However, this is a regression. 254.gap worked in the 2014.04 release at -O3. linaro- arm-linux- gnueabihf- 4.9-2014. 05_linux/ bin/arm- linux-gnueabihf -gcc -O3 -march=armv7-a -mfpu=vfpv3-d16 -fno-use- linker- plugin -flto -marm -mfloat-abi=hard -ffast-math -ftree-vectorize -g -static -static agcollec.o aggroup.o blister.o coding.o costab.o cyclotom.o eval.o finfield.o function.o gap.o gasman.o idents.o integer.o list.o pcpresen.o permutat.o plist.o polynom.o range.o rational.o read.o record.o scanner.o set.o statemen.o string.o system.o tietze.o unknown.o vecffe.o vector.o word.o -lm -o gap
/opt/gcc-