Includes header documentation and initial set of include directives.
2020-02-03 Bill Schmidt <wschm...@linux.ibm.com>
* config/rs6000/rs6000-genbif.c: New file.
---
gcc/config/rs6000/rs6000-genbif.c | 124 ++++++++++++++++++++++++++++++
1 file changed, 124 insertions(+)
create mode 100644 gcc/config/rs6000/rs6000-genbif.c
diff --git a/gcc/config/rs6000/rs6000-genbif.c
b/gcc/config/rs6000/rs6000-genbif.c
new file mode 100644
index 00000000000..a53209ed040
--- /dev/null
+++ b/gcc/config/rs6000/rs6000-genbif.c
@@ -0,0 +1,124 @@
+/* Generate built-in function initialization and recognition for Power.
+ Copyright (C) 2020 Free Software Foundation, Inc.
+ Contributed by Bill Schmidt, IBM <wschm...@linux.ibm.com>
+
+This file is part of GCC.
+
+GCC is free software; you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation; either version 3, or (at your option) any later
+version.
+
+GCC is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
+for more details.
+
+You should have received a copy of the GNU General Public License
+along with GCC; see the file COPYING3. If not see
+<http://www.gnu.org/licenses/>. */
+
+/* This program generates built-in function initialization and
+ recognition code for Power targets, based on text files that
+ describe the built-in functions and vector overloads:
+
+ rs6000-bif.def Table of built-in functions
+ rs6000-overload.def Table of overload functions
+
+ Both files group similar functions together in "stanzas," as
+ described below.
+
+ Each stanza in the built-in function file starts with a line
+ identifying the target mask for which the group of functions is
+ permitted, with the mask in square brackets. This is the only
+ information allowed on the stanza header line, other than
+ whitespace. Following the stanza header are two lines for each
+ function: the prototype line and the attributes line. The
+ prototype line has this format, where the square brackets
+ indicate optional information and angle brackets indicate
+ required information:
+
+ [kind] <return-type> <bif-name> (<argument-list>);
+
+ Here [kind] can be one of "const", "pure", or "math";
+ <return-type> is a legal type for a built-in function result;
+ <bif-name> is the name by which the function can be called;
+ and <argument-list> is a comma-separated list of legal types
+ for built-in function arguments. The argument list may be
+ empty, but the parentheses and semicolon are required.
+
+ The attributes line looks like this:
+
+ <bif-id> <bif-pattern> {<attribute-list>}
+
+ Here <bif-id> is a unique internal identifier for the built-in
+ function that will be used as part of an enumeration of all
+ built-in functions; <bif-pattern> is the define_expand or
+ define_insn that will be invoked when the call is expanded;
+ and <attribute-list> is a comma-separated list of special
+ conditions that apply to the built-in function. The attribute
+ list may be empty, but the braces are required.
+
+ Attributes are strings, such as these:
+
+ init Process as a vec_init function
+ set Process as a vec_set function
+ ext Process as a vec_extract function
+ nosoft Not valid with -msoft-float
+ ldv Needs special handling for vec_ld semantics
+ stv Needs special handling for vec_st semantics
+ reve Needs special handling for element reversal
+ abs Needs special handling for absolute value
+ pred Needs special handling for comparison predicates
+ htm Needs special handling for transactional memory
+
+ An example stanza might look like this:
+
+[TARGET_ALTIVEC]
+ const vector signed char __builtin_altivec_abs_v16qi (vector signed char);
+ ABS_V16QI absv16qi2 {abs}
+ const vector signed short __builtin_altivec_abs_v8hi (vector signed short);
+ ABS_V8HI absv8hi2 {abs}
+
+ Note the use of indentation, which is recommended but not required.
+
+ The overload file has more complex stanza headers. Here the stanza
+ represents all functions with the same overloaded function name:
+
+ [<overload-id>, <external-name>, <internal-name>]
+
+ Here the square brackets are part of the syntax, <overload-id> is a
+ unique internal identifier for the overload that will be used as part
+ of an enumeration of all overloaded functions; <external-name> is the
+ name that will appear as a #define in altivec.h; and <internal-name>
+ is the name that is overloaded in the back end.
+
+ Each function entry again has two lines. The first line is again a
+ prototype line (this time without [kind]):
+
+ <return-type> <internal-name> (<argument-list>);
+
+ The second line contains only one token: the <bif-id> that this
+ particular instance of the overloaded function maps to. It must
+ match a token that appears in the bif file.
+
+ An example stanza might look like this:
+
+[VEC_ABS, vec_abs, __builtin_vec_abs]
+ vector signed char __builtin_vec_abs (vector signed char);
+ ABS_V16QI
+ vector signed short __builtin_vec_abs (vector signed short);
+ ABS_V8HI
+
+ Blank lines may be used as desired in these files. If it's desirable,
+ C-style comments are allowable provided that the file is run through
+ the preprocessor by the build system prior to feeding it to this
+ program. */
+
+#include <stdio.h>
+#include <stdlib.h>
+#include <stdarg.h>
+#include <stdint.h>
+#include <ctype.h>
+#include <string.h>
+#include <assert.h>
--
2.17.1
