------- Comment #3 from bonzini at gnu dot org 2006-12-14 17:46 ------- Don't confuse __builtin_altivec_vmuloub (only used by middle-end, has the "wrong" types) with __builtin_vec_vmuloub (cannot be created by middle-end, lowered by the C front-end to __builtin_altivec_vmuloub after checking the parameter types are correct).
The types of __builtin_altivec_vmuloub don't have anything to do with what the PIM manual says. And anyway, __builtin_altivec_vmuloub can have the "wrong" types because it is always decorated with the appropriate NOP_EXPRs: this may be bad from a memory usage point of view, but it is not incorrect. Also, note that it has always worked this way: what changed is *who* does the lowering (either a preprocessor macro vec_vmuloub, or resolve_overloaded_builtin starting from builtin __builtin_vec_vmuloub). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30210
