On 12/22/09, Daniel Jacobowitz <[email protected]> wrote:
> in a patch I'm working on for ARM cmpdi patterns, I ended up needing
> "cmpdi_lhs_operand" and "cmpdi_rhs_operand" predicates because Cirrus
> and VFP targets accept different constants. Automatically generating
> that would be a bit excessive though.
I wouldn't bother implementaing that if the VFP/Cirrus conflict is the
only thing that needs that.
GCC's has never been able to generate working code for Cirrus
MaverickCrunch for over a dozen separate reasons, from incorrect use
of the way the Maverick sets the condition codes to hardware bugs in
the 64-bit instructions (or in the way GCC uses them).
I eventually cooked up over a dozen patches to make 4.[23] generate
reliable crunch floating point code but if you enable the 64-bit insns
it still fails the openssl testsuite.
M
