This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: A Far Less Ambitous AltiVec patch
Ziemowit Laski <zlaski@apple.com> writes:
| In C++, it is perfectly legal for someone to overload a function as
| follows:
|
| void foo(vector unsigned short vec) { ... }
| void foo(vector bool short vec) { ... }
| void foo(vector pixel vec) { ... }
|
| Under the generic vector regime currently supported by FSF gcc, all 3
| functions will appear
| to have exactly the same signature, since the 'vec' argument for each
| gets lowered to
| an unsigned_V8HI_type_node.
That is no right. If they are overloads then they should mangle
differently. That is the primary purpose of mangling.
So, instead of having a vendor specifc thing in a corner, I think it is
far better to fix the bug.
-- Gaby