Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ben Elliston" <bje@au1.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: remove f-exp.y warnings
Date: Sat, 11 Dec 2004 11:19:00 -0000	[thread overview]
Message-ID: <20041211054016.GA313@namadgi> (raw)

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

This patch eliminates a handful of warnings from bison.  Okay for
mainline?

Ben


2004-12-11  Ben Elliston  <bje@au.ibm.com>

	* f-exp.y (typename): Remove unused nonterminal.
	(name): Likewise.

Index: f-exp.y
===================================================================
RCS file: /home/bje/src-cvs/src/gdb/f-exp.y,v
retrieving revision 1.15
diff -u -p -r1.15 f-exp.y
--- f-exp.y	28 Jul 2004 15:49:03 -0000	1.15
+++ f-exp.y	11 Dec 2004 05:37:42 -0000
@@ -177,9 +177,7 @@ static int parse_number (char *, int, in
 %token <lval> BOOLEAN_LITERAL
 %token <ssym> NAME 
 %token <tsym> TYPENAME
-%type <sval> name
 %type <ssym> name_not_typename
-%type <tsym> typename
 
 /* A NAME_OR_INT is a symbol which is not known in the symbol table,
    but which would parse as a valid number in the current input radix.
@@ -597,9 +595,6 @@ typebase  /* Implements (approximately):
 			{ $$ = builtin_type_f_complex_s32;}
 	;
 
-typename:	TYPENAME
-	;
-
 nonempty_typelist
 	:	type
 		{ $$ = (struct type **) malloc (sizeof (struct type *) * 2);
@@ -611,14 +606,6 @@ nonempty_typelist
 		  $$ = (struct type **) realloc ((char *) $1, len);
 		  $$[$<ivec>$[0]] = $3;
 		}
-	;
-
-name	:	NAME
-			{ $$ = $1.stoken; }
-	|	TYPENAME
-			{ $$ = $1.stoken; }
-	|	NAME_OR_INT
-			{ $$ = $1.stoken; }
 	;
 
 name_not_typename :	NAME

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-12-11  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 11:19 Ben Elliston [this message]
2004-12-12 17:00 ` Andrew Cagney

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=20041211054016.GA313@namadgi \
    --to=bje@au1.ibm.com \
    --cc=gdb-patches@sources.redhat.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