From: Ian Lance Taylor <iant@google.com>
To: zhang qingshan <steven.zhang54373@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: How to get the full list of GCC builtins?
Date: Fri, 30 Sep 2011 07:26:00 -0000 [thread overview]
Message-ID: <mcrhb3u5zv0.fsf@coign.corp.google.com> (raw)
In-Reply-To: <CALBibxnwzTgs3R1vQU8KmTQ6onTRTjZ_gm1h1hoXWj5ef6hJ_g@mail.gmail.com> (zhang qingshan's message of "Fri, 30 Sep 2011 13:01:01 +0800")
zhang qingshan <steven.zhang54373@gmail.com> writes:
> Does gcc have any doc/method to get all the builtins it supports? Thanks.
You can read the documentation, which I believe lists all of them except
a few which are used internally which are intentionally undocumented.
Or you can look at the source file gcc/builtins.def.
Ian
prev parent reply other threads:[~2011-09-30 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 6:20 zhang qingshan
2011-09-30 7:26 ` Ian Lance Taylor [this message]
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=mcrhb3u5zv0.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=steven.zhang54373@gmail.com \
/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).