Skip to contentSkip to conversation

internal compiler error while building valgrind ptest

DISCUSSION Carlos Rafael Giani 2 participants 2 messages Sep 21, 2014 – Sep 22, 2014

lore
Share & tools
lore
#0 lore raw

Hello,

I am trying to build valgrind. This ptest compile error occurs:

arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/home/build/OE/poky/build/tmp/sysroots/cubox-i -DHAVE_CONFIG_H -I. -I/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm -I../../.. -I/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0 -I/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/include -I/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/coregrind -I../../../include -I/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 -DVGPV_arm_linux_vanilla=1 -Winline -Wall -Wshadow -g -Wno-long-long -O2 -pipe -g -feliminate-unused-debug-types -Wwrite-strings -fno-stack-protector -Wno-write-strings -c -o vcvt_fixed_float_VFP.o /home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c: In function 'f64_to_s32_imm1':
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:147:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
return *(ULong*)(&block[3]);
^
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c: In function 'f64_to_s32_imm32':
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:162:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
return *(ULong*)(&block[3]);
^
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c: In function 'f64_to_u32_imm1':
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:187:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
return *(ULong*)(&block[3]);
^
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c: In function 'f64_to_u32_imm32':
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:202:3: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
return *(ULong*)(&block[3]);
^
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c: In function 's32_to_f32_imm1':
/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:12:1: internal compiler error: Max. number of generated reload insns per insn is achieved (90)

}
^

If I remove ptest from the valgrind recipe, everything is OK.

Has anybody seen a similar error?

#1 lore raw
Quoted 4 lines · Carlos Rafael Giani

/home/build/OE/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/valgrind/3.9.0-r8/valgrind-3.9.0/none/tests/arm/vcvt_fixed_float_VFP.c:147:3:
warning: dereferencing type-punned pointer will break strict-aliasing rules
[-Wstrict-aliasing]
return *(ULong*)(&block[3]);

All we do at compile time when ptest is enabled is run "make check", so you might want to report this upstream.

Ross