This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Why DECL_BUILT_IN and DECL_IS_BUILTIN?
- From: "Paulo Matos" <pmatos at broadcom dot com>
- To: "Richard Biener" <richard dot guenther at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 3 Sep 2013 12:19:37 +0000
- Subject: RE: Why DECL_BUILT_IN and DECL_IS_BUILTIN?
- Authentication-results: sourceware.org; auth=none
- References: <19EB96622A777C4AB91610E763265F462B2BC8 at SJEXCHMB14 dot corp dot ad dot broadcom dot com> <CAFiYyc2sSXOZP1DZgL3KwkMKApB7QEuSKCR352m3KeB=HDL0Ug at mail dot gmail dot com> <19EB96622A777C4AB91610E763265F462B2C29 at SJEXCHMB14 dot corp dot ad dot broadcom dot com> <CAFiYyc1ENcX=qHjnsxod_AE-zwghvU=RsWQy3yoKiW7RyCt1_A at mail dot gmail dot com>
> -----Original Message-----
> From: Richard Biener [mailto:richard.guenther@gmail.com]
> Sent: 03 September 2013 12:55
> To: Paulo Matos
> Cc: gcc@gcc.gnu.org
> Subject: Re: Why DECL_BUILT_IN and DECL_IS_BUILTIN?
>
> DECL_IS_BUILTIN is true if the decl was created by the frontend / backend
> rather than by user code (indicated by source location). DECL_BUILT_IN
> is true if the decl represents a function of the standard library, a
> builtin that is
> recognized by optimization / expansion. User declared prototypes of
> C library functions are not DECL_IS_BUILTIN but may be DECL_BUILT_IN.
>
> Richard.
>
Thanks for the explanation.
Cheers.