public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at crg4 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/66970] New: Add __has_builtin() macro
Date: Wed, 22 Jul 2015 14:58:00 -0000	[thread overview]
Message-ID: <bug-66970-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66970

            Bug ID: 66970
           Summary: Add __has_builtin() macro
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gcc at crg4 dot com
  Target Milestone: ---

gcc has a large collection of builtins (intrinsics), as listed at
https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html

A useful feature would be a __has_builtin() macro, as implemented in clang:
http://clang.llvm.org/docs/LanguageExtensions.html#feature-checking-macros

This would allow feature detection rather than requiring checks against
compiler names and versions.

Support for this enhancement was expressed on the mailing list (Sep 2012)
http://comments.gmane.org/gmane.comp.gcc.help/42610
but it looks like it was never submitted as a bug.


             reply	other threads:[~2015-07-22 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 14:58 gcc at crg4 dot com [this message]
2015-07-26  9:21 ` [Bug c/66970] " pinskia at gcc dot gnu.org

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=bug-66970-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).