This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/28921] vector of a typedef applies the vector to the inner most type instead of erroring/warning out that vector does not apply
- From: "egallager at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 25 Jul 2017 00:21:35 +0000
- Subject: [Bug c/28921] vector of a typedef applies the vector to the inner most type instead of erroring/warning out that vector does not apply
- Auto-submitted: auto-generated
- References: <bug-28921-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28921
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-07-25
CC| |egallager at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |8.0
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #0)
> Testcase:
> typedef char *cptr;
>
> char *a;
>
> __attribute__ ((vector_size(16))) cptr t;
>
> int f(void)
> {
>
> __attribute__ ((vector_size(16))) int t1 =
> (__attribute__ ((vector_size(16))) int )t;
> }
>
> We get an error about converting t to a vector int but t looks to me a
> vector of a char pointer. This happens with both the C and C++ front-ends.
Confirmed.