This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/42664] ICE on compilation of polyhedron benchmarks with -mfma4
- From: "ubizjak at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jan 2010 20:47:46 -0000
- Subject: [Bug fortran/42664] ICE on compilation of polyhedron benchmarks with -mfma4
- References: <bug-42664-12304@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from ubizjak at gmail dot com 2010-01-08 20:47 -------
(In reply to comment #0)
> The attached reduced test case derived from ac.f90 in the polyhedron benchmark
> suite gives and ICE when compiled with gfortran 4.5 using -O3 -mfma4. This ICE
> showed up in gcc 4.5 rev 154969 with the following check in:
>
> 2009-12-02 Richard Henderson <rth@redhat.com>
>
> * config/i386/i386.c (ix86_fixup_binary_operands): For FMA4, force
> all operands into registers.
Do we actually need this fixup after all input operands of FMA4 insn were
changed to "nonimmediate operand" in
2009-12-03 Sebastian Pop <sebastian.pop@amd.com>
Richard Henderson <rth@redhat.com>
* config/i386/i386-protos.h (ix86_fma4_valid_op_p): Remove.
* config/i386/i386.c (ix86_fma4_valid_op_p): Remove.
* config/i386/i386.md: Do not use ix86_fma4_valid_op_p.
* config/i386/sse.md (fma4_*): Remove alternative with operand 1
matching a memory access. Do not use ix86_fma4_valid_op_p.
(xop_*): Same.
Do not use ix86_fma4_valid_op_p in FMA4 and XOP splitters.
and
2009-12-07 Sebastian Pop <sebastian.pop@amd.com>
* config/i386/sse.md: Remove all FMA4 splitters.
Allow the second operand of FMA4 insns to be a nonimmediate.
Fix comments punctuation.
I'd say that after these commits, 2009-12-02 fixup is not needed anymore and
should be removed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42664