This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Prototypes for builtin functions
- From: "Paulo Matos" <pmatos at broadcom dot com>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 2 Sep 2013 14:21:46 +0000
- Subject: RE: Prototypes for builtin functions
- Authentication-results: sourceware.org; auth=none
- References: <19EB96622A777C4AB91610E763265F462B1F85 at SJEXCHMB14 dot corp dot ad dot broadcom dot com>
> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf Of Paulo
> Matos
> Sent: 29 August 2013 11:44
> To: gcc@gcc.gnu.org
> Subject: Prototypes for builtin functions
>
> Hi,
>
> I would like to hear how other architectures organize their builtin/intrinsic
> headers.
>
> Until recently we had a header that would look like:
>
> /* Types */
> typedef char V8B __attribute__ ((vector_size (8)));
> ...
>
> /* Prototypes */
> extern V8B __vec_put_v8b (V8B B, char C, unsigned char D);
> ...
Besides pinging this question for some sort of answer, isn't true that if a declaration is marked extern, then the tree location for the decl shouldn't be changed?
--
Paulo Matos