https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83789
--- Comment #12 from Kaushikp ---
>> we're getting duplicate named patterns.
Yes, it does generate multiple patters for the concerned built-ins causing
toolchain build failure.
I think it's trying to force the same pattern for 32-bit which exist
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83789
--- Comment #5 from Kaushikp ---
>> Kaushik: is this fixed with r256762?
No. The testcase still fails with internal compiler error: Segmentation fault.
This revision (r256762) dated 16th Jan 2018 still calls
'CODE_FOR_altivec_lvx_v4si_2op' insn
f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83789
--- Comment #1 from Kaushikp ---
Just some additional info on this issue,
The powerpc-elf-gcc did not have any issues compiling this testcase with
identical options on gcc-7.2.0;
powerpc-linux-gcc generated segmentation fault;
powerpc64-linux-
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: kaushik.phatak at kpitcummins dot com
Target Milestone: ---
Regression testcase gcc.target/powerpc/altivec-4.c fails for powerpc gcc-7
onwards.
$powerpc-linux-gcc -m32 -mhard-float -maltivec altivec
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: kaushik.phatak at kpitcummins dot com
Results are as below:
FAIL: gcc.target/arm/vfp-1.c scan-assembler fmacs
FAIL: gcc.target/arm/vfp-1.c scan-assembler fmscs
FAIL
