This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH] Update comment in gcc/builtins.def
- From: Alexey Neyman <alex dot neyman at auriga dot ru>
- To: gcc-patches at gcc dot gnu dot org
- Date: Wed, 2 Mar 2005 20:42:19 +0300
- Subject: [PATCH] Update comment in gcc/builtins.def
- Organization: Auriga
Hi,
the recently-introduced COND argument was not described in the
comment.
Regards,
Alexey.
--
Wouldn't you know it, get too perfect
and you wrap right around to evil.
-- Pkunks, SC2
2005-03-02 Alexey Neyman <alex.neyman@auriga.ru>
* gcc/builtins.def: Update the comment for DEF_BUILTIN.
Index: gcc/builtins.def
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/builtins.def,v
retrieving revision 1.95
diff -u -r1.95 builtins.def
--- gcc/builtins.def 10 Feb 2005 18:59:04 -0000 1.95
+++ gcc/builtins.def 2 Mar 2005 17:38:15 -0000
@@ -23,7 +23,7 @@
/* Before including this file, you should define a macro:
DEF_BUILTIN (ENUM, NAME, CLASS, TYPE, LIBTYPE, BOTH_P,
- FALLBACK_P, NONANSI_P, ATTRS, IMPLICIT)
+ FALLBACK_P, NONANSI_P, ATTRS, IMPLICIT, COND)
This macro will be called once for each builtin function. The
ENUM will be of type `enum built_in_function', and will indicate
@@ -61,7 +61,12 @@
define it's meaning. When user uses floorf we may assume that the
floorf has the meaning we expect, but we can't produce floorf by
simplifying floor((double)float) since the runtime need not implement
- it. */
+ it.
+
+ If COND is true, then the builtin can be initialized by language-
+ specific function. Otherwise, it should be left for the
+ build_common_builtin_nodes() to be initialized. See the c-common.c
+ file. */
/* A GCC builtin (like __builtin_saveregs) is provided by the
compiler, but does not correspond to a function in the standard