This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC compiler intrinsics.
- To: andrew_g_hanson at yahoo dot com, gcc at gcc dot gnu dot org
- Subject: Re: GCC compiler intrinsics.
- From: Mike Stump <mrs at windriver dot com>
- Date: Thu, 4 May 2000 06:23:02 -0700 (PDT)
Don't mime encode, don't send html to the list, thanks.
> From: "Andy Hanson" <andrew_g_hanson@yahoo.com>
> To: <gcc@gcc.gnu.org>
> Date: Thu, 4 May 2000 04:57:11 -0500
> he fact that memset was unresolved, implied that memset isn't a
> compiler intrinsic.
Update your compiler?
> Now the big question is where to start. I did a little digging
> through the egcs release, and binutils, and I can't seem to see
> where intrinsics like strcpy get processed by the compiler.
Well, you can do an ls in the gcc directory, and notice:
builtins.c
Sounds like it might be found builtins, if I had to guess. Or, you
could have run M-x grep in emacs and looked for memset, and found:
builtin_function ("__builtin_memset", memset_ftype, BUILT_IN_MEMSET,
builtin_function ("memset", memset_ftype, BUILT_IN_MEMSET,
in about 1 second.