From: Bill Schmidt <wschmidt@linux.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: segher@kernel.crashing.org, dje.gcc@gmail.com, willschm@linux.ibm.com
Subject: [PATCH 07/28] rs6000: Add functions for matching types, part 3 of 3
Date: Wed, 17 Jun 2020 14:46:30 -0500 [thread overview]
Message-ID: <a068e4442e85e1fb1cabd2bf5013a4914a055d63.1592419212.git.wschmidt@linux.ibm.com> (raw)
In-Reply-To: <cover.1592419211.git.wschmidt@linux.ibm.com>
In-Reply-To: <cover.1592419211.git.wschmidt@linux.ibm.com>
2020-06-17 Bill Schmidt <wschmidt@linux.ibm.com>
* config/rs6000/rs6000-gen-builtins.c (restriction): New enum.
(typeinfo): Add restriction field.
(match_const_restriction): Implement.
---
gcc/config/rs6000/rs6000-gen-builtins.c | 136 ++++++++++++++++++++++++
1 file changed, 136 insertions(+)
diff --git a/gcc/config/rs6000/rs6000-gen-builtins.c b/gcc/config/rs6000/rs6000-gen-builtins.c
index e38f3af9c7a..e4b08ee5036 100644
--- a/gcc/config/rs6000/rs6000-gen-builtins.c
+++ b/gcc/config/rs6000/rs6000-gen-builtins.c
@@ -189,6 +189,21 @@ enum basetype {
BT_IBM128
};
+/* Ways in which a const int value can be restricted. RES_BITS indicates
+ that the integer is restricted to val1 bits, interpreted as an unsigned
+ number. RES_RANGE indicates that the integer is restricted to values
+ between val1 and val2, inclusive. RES_VAR_RANGE is like RES_RANGE, but
+ the argument may be variable, so it can only be checked if it is constant.
+ RES_VALUES indicates that the integer must have one of the values val1
+ or val2. */
+enum restriction {
+ RES_NONE,
+ RES_BITS,
+ RES_RANGE,
+ RES_VAR_RANGE,
+ RES_VALUES
+};
+
/* Type modifiers for an argument or return type. */
struct typeinfo {
char isvoid;
@@ -201,6 +216,7 @@ struct typeinfo {
char ispointer;
char isopaque;
basetype base;
+ restriction restr;
int val1;
int val2;
};
@@ -434,6 +450,126 @@ match_basetype (typeinfo *typedata)
static int
match_const_restriction (typeinfo *typedata)
{
+ int oldpos = pos;
+ if (linebuf[pos] == '<')
+ {
+ safe_inc_pos ();
+ oldpos = pos;
+ int x = match_integer ();
+ if (x == MININT)
+ {
+ (*diag) ("malformed integer at column %d.\n", oldpos + 1);
+ return 0;
+ }
+ consume_whitespace ();
+ if (linebuf[pos] == '>')
+ {
+ typedata->restr = RES_BITS;
+ typedata->val1 = x;
+ safe_inc_pos ();
+ return 1;
+ }
+ else if (linebuf[pos] != ',')
+ {
+ (*diag) ("malformed restriction at column %d.\n", pos + 1);
+ return 0;
+ }
+ safe_inc_pos ();
+ oldpos = pos;
+ int y = match_integer ();
+ if (y == MININT)
+ {
+ (*diag) ("malformed integer at column %d.\n", oldpos + 1);
+ return 0;
+ }
+ typedata->restr = RES_RANGE;
+ typedata->val1 = x;
+ typedata->val2 = y;
+
+ consume_whitespace ();
+ if (linebuf[pos] != '>')
+ {
+ (*diag) ("malformed restriction at column %d.\n", pos + 1);
+ return 0;
+ }
+ safe_inc_pos ();
+ }
+ else if (linebuf[pos] == '{')
+ {
+ safe_inc_pos ();
+ oldpos = pos;
+ int x = match_integer ();
+ if (x == MININT)
+ {
+ (*diag) ("malformed integer at column %d.\n", oldpos + 1);
+ return 0;
+ }
+ consume_whitespace ();
+ if (linebuf[pos] != ',')
+ {
+ (*diag) ("missing comma at column %d.\n", pos + 1);
+ return 0;
+ }
+ safe_inc_pos ();
+ consume_whitespace ();
+ oldpos = pos;
+ int y = match_integer ();
+ if (y == MININT)
+ {
+ (*diag) ("malformed integer at column %d.\n", oldpos + 1);
+ return 0;
+ }
+ typedata->restr = RES_VALUES;
+ typedata->val1 = x;
+ typedata->val2 = y;
+
+ consume_whitespace ();
+ if (linebuf[pos] != '}')
+ {
+ (*diag) ("malformed restriction at column %d.\n", pos + 1);
+ return 0;
+ }
+ safe_inc_pos ();
+ }
+ else
+ {
+ assert (linebuf[pos] == '[');
+ safe_inc_pos ();
+ oldpos = pos;
+ int x = match_integer ();
+ if (x == MININT)
+ {
+ (*diag) ("malformed integer at column %d.\n", oldpos + 1);
+ return 0;
+ }
+ consume_whitespace ();
+ if (linebuf[pos] != ',')
+ {
+ (*diag) ("missing comma at column %d.\n", pos + 1);
+ return 0;
+ }
+ safe_inc_pos ();
+ consume_whitespace ();
+ oldpos = pos;
+ int y = match_integer ();
+ if (y == MININT)
+ {
+ (*diag) ("malformed integer at column %d.\n", oldpos + 1);
+ return 0;
+ }
+ typedata->restr = RES_VAR_RANGE;
+ typedata->val1 = x;
+ typedata->val2 = y;
+
+ consume_whitespace ();
+ if (linebuf[pos] != ']')
+ {
+ (*diag) ("malformed restriction at column %d.\n", pos + 1);
+ return 0;
+ }
+ safe_inc_pos ();
+ }
+
return 1;
}
--
2.17.1
next prev parent reply other threads:[~2020-06-17 19:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 19:46 [PATCH 00/28] rs6000: Auto-generate builtins from descriptions Bill Schmidt
2020-06-17 19:46 ` [PATCH 01/28] rs6000: Initial create of rs6000-gen-builtins.c Bill Schmidt
2020-06-17 19:46 ` [PATCH 02/28] rs6000: Add initial input files Bill Schmidt
2020-06-17 19:46 ` [PATCH 03/28] rs6000: Add file support and functions for diagnostic support Bill Schmidt
2020-06-17 19:46 ` [PATCH 04/28] rs6000: Add helper functions for parsing Bill Schmidt
2020-06-17 19:46 ` [PATCH 05/28] rs6000: Add functions for matching types, part 1 of 3 Bill Schmidt
2020-06-17 19:46 ` [PATCH 06/28] rs6000: Add functions for matching types, part 2 " Bill Schmidt
2020-06-17 19:46 ` Bill Schmidt [this message]
2020-06-17 19:46 ` [PATCH 08/28] rs6000: Red-black tree implementation for balanced tree search Bill Schmidt
2020-06-17 19:46 ` [PATCH 09/28] rs6000: Main function with stubs for parsing and output Bill Schmidt
2020-06-17 19:46 ` [PATCH 10/28] rs6000: Parsing built-in input file, part 1 of 3 Bill Schmidt
2020-06-17 19:46 ` [PATCH 11/28] rs6000: Parsing built-in input file, part 2 " Bill Schmidt
2020-06-17 19:46 ` [PATCH 12/28] rs6000: Parsing built-in input file, part 3 " Bill Schmidt
2020-06-17 19:46 ` [PATCH 13/28] rs6000: Parsing of overload input file Bill Schmidt
2020-06-17 19:46 ` [PATCH 14/28] rs6000: Build and store function type identifiers Bill Schmidt
2020-06-17 19:46 ` [PATCH 15/28] rs6000: Write output to the vector definition include file Bill Schmidt
2020-06-17 19:46 ` [PATCH 16/28] rs6000: Write output to the builtins header file Bill Schmidt
2020-06-17 19:46 ` [PATCH 17/28] rs6000: Write output to the builtins init file, part 1 of 3 Bill Schmidt
2020-06-17 19:46 ` [PATCH 18/28] rs6000: Write output to the builtins init file, part 2 " Bill Schmidt
2020-06-17 19:46 ` [PATCH 19/28] rs6000: Write output to the builtins init file, part 3 " Bill Schmidt
2020-06-17 19:46 ` [PATCH 20/28] rs6000: Incorporate new builtins code into the build machinery Bill Schmidt
2020-06-17 19:46 ` [PATCH 21/28] rs6000: Add remaining MASK_ALTIVEC builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 22/28] rs6000: Add MASK_VSX builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 23/28] rs6000: Add available-everywhere and ancient builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 24/28] rs6000: Add Power7 builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 25/28] rs6000: Add MASK_P8_VECTOR builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 26/28] rs6000: Add MASK_P9_VECTOR and MASK_P9_MISC builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 27/28] rs6000: Add remaining builtins Bill Schmidt
2020-06-17 19:46 ` [PATCH 28/28] rs6000: Add comments to help with transition Bill Schmidt
2020-06-18 16:08 ` [PATCH 00/28] rs6000: Auto-generate builtins from descriptions will schmidt
2020-06-18 22:01 ` Bill Schmidt
2020-06-18 22:48 ` will schmidt
2020-06-23 20:21 ` Bill Schmidt
2020-07-01 14:47 ` Bill Schmidt
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=a068e4442e85e1fb1cabd2bf5013a4914a055d63.1592419212.git.wschmidt@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=willschm@linux.ibm.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).