From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-412568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27748 invoked by alias); 18 Jan 2013 09:39:11 -0000
Received: (qmail 25805 invoked by uid 48); 18 Jan 2013 09:38:25 -0000
From: "Tim.Northover at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56025] New: ARM NEON polynomial types have broken overload resolution
Date: Fri, 18 Jan 2013 09:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Tim.Northover at arm dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-56025-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2013-01/txt/msg01687.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56025

             Bug #: 56025
           Summary: ARM NEON polynomial types have broken overload
                    resolution
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Tim.Northover@arm.com


While investigating bug #56024, we discovered this problem in the same area.
Essentially, GCC has semi-special builtin types to cover poly8_t and poly16_t
defined in arm_neon.h.

These types are used by G++ when calculating the overload resolution. The
following two functions can both be defined with no issues in the front-end:

#include <arm_neon.h>
void foo(short s) {}
void foo(__builtin_neon_poly16 s) {}

However, in the resulting assembly they are both mangled as _Z3foos, which
causes a conflict.

This mangling area is likely to be affected by any change fixing 56024, so a
sensible combined solution might be a good idea.