On Tue, Dec 22, 2009 at 04:24:01PM +0000, Martin Guy wrote: > 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.
Interesting, I knew you had a lot of Cirrus patches but I didn't realize the state of the checked-in code was so bad. Is what's there useful or actively harmful? -- Daniel Jacobowitz CodeSourcery
