public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56025] ARM NEON polynomial types have broken overload resolution
Date: Tue, 06 Jan 2015 17:14:00 -0000 [thread overview]
Message-ID: <bug-56025-4-lBmv60G1FA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56025-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56025
Tejas Belagod <belagod at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |belagod at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #2 from Tejas Belagod <belagod at gcc dot gnu.org> ---
(In reply to Tim Northover from comment #0)
> 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.
This should now be fixed. Now mangled as _Z3foos and _Z3foo10__Poly16_t
respectively.
.cpu generic+fp+simd
.file "gpp.cpp"
.text
.align 2
.p2align 3,,7
.global _Z3foos
.type _Z3foos, %function
_Z3foos:
.LFB3026:
.cfi_startproc
ret
.cfi_endproc
.LFE3026:
.size _Z3foos, .-_Z3foos
.align 2
.p2align 3,,7
.global _Z3foo10__Poly16_t
.type _Z3foo10__Poly16_t, %function
_Z3foo10__Poly16_t:
.LFB3027:
.cfi_startproc
ret
.cfi_endproc
.LFE3027:
.size _Z3foo10__Poly16_t, .-_Z3foo10__Poly16_t
.ident "GCC: (unknown) 5.0.0 20141229 (experimental)"
next prev parent reply other threads:[~2015-01-06 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 9:39 [Bug c++/56025] New: " Tim.Northover at arm dot com
2013-01-18 9:52 ` [Bug c++/56025] " rearnsha at gcc dot gnu.org
2015-01-06 17:14 ` belagod at gcc dot gnu.org [this message]
2015-01-06 17:21 ` [Bug target/56025] " belagod at gcc dot gnu.org
2015-01-07 14:37 ` belagod at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-56025-4-lBmv60G1FA@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).