------- Comment #3 from rguenth at gcc dot gnu dot org 2010-02-17 21:30 ------- (In reply to comment #2) > I don't see why you want to deal with special cases in the library instead of > the optimizers: indeed, your *very* analysis shows that the missed > optimization > is happening in tree-complex.c and improving it would benefit *many* more uses > outside the library.
Well, but float * complex<float> isn't the same as complex<float> * complex<float>. But the library (and also C promotion if you write that in literal C) presents us with complex<float> * complex<float>. Which we have to handle according to the standard (thus "slow"). So either this is WONTFIX or a library issue. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43108
