public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54130] Recognize builtins with bool return type Date: Tue, 31 Jul 2012 14:43:00 -0000 [thread overview] Message-ID: <bug-54130-4-ovHOe4b4LQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54130-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54130 --- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-07-31 14:43:18 UTC --- In C it's a macro not a function and there is no guarantee that there exists a function with that name, or what the semantics of such a function would be. In C++, unlike C, I think you are required to include the standard headers to get any standard library facilities. (For C, you can use functions, not macros, without including headers if the functions' prototypes do not involve any type defined in a standard header, only built-in C types.)
next prev parent reply other threads:[~2012-07-31 14:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-30 20:43 [Bug c++/54130] New: " glisse at gcc dot gnu.org 2012-07-31 9:32 ` [Bug c++/54130] " rguenth at gcc dot gnu.org 2012-07-31 9:38 ` glisse at gcc dot gnu.org 2012-07-31 14:43 ` joseph at codesourcery dot com [this message] 2012-07-31 19:20 ` glisse at gcc dot gnu.org 2012-07-31 20:00 ` joseph at codesourcery dot com 2012-07-31 20:13 ` glisse at gcc dot gnu.org 2012-07-31 22:13 ` joseph at codesourcery dot com 2012-08-01 5:51 ` glisse at gcc dot gnu.org 2012-08-01 9:23 ` glisse at gcc dot gnu.org 2012-08-01 9:27 ` rguenth at gcc dot gnu.org 2012-08-01 9:29 ` rguenth at gcc dot gnu.org 2012-08-01 9:49 ` glisse at gcc dot gnu.org 2012-08-01 9:52 ` glisse at gcc dot gnu.org 2012-08-01 15:41 ` joseph at codesourcery dot com 2012-08-01 16:31 ` redi 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-54130-4-ovHOe4b4LQ@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: linkBe 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).