From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix building with yacc
Date: Wed, 05 Feb 2014 12:37:00 -0000 [thread overview]
Message-ID: <201402051237.s15CbhlK028161@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20140205021312.GB5485@adacore.com> (message from Joel Brobecker on Wed, 5 Feb 2014 06:13:12 +0400)
> Date: Wed, 5 Feb 2014 06:13:12 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> Hi Mark,
>
> > OpenBSD yacc doesn't use YYPRINT, so we end up with gcc complaining
> > that c_print_token is defined but not used. As far as I can determine
> > YYPRINT is a bison-ism, so the diff below wraps c_print_token in
> > #ifdef YYBISON.
> >
> > ok?
>
> I don't know bison much to really review the patch, but I think
> that you meant c_print_token to remain static, right? (see below)
> Aside from that, the change looks OK to me.
Oops. Thanks for spotting that. Below is what I ended up committing:
From 12c5175d68a840960e4cf7d3001c926f15c4d006 Mon Sep 17 00:00:00 2001
From: Mark Kettenis <kettenis@gnu.org>
Date: Wed, 5 Feb 2014 13:30:33 +0100
Subject: [PATCH] Avoid bison-isms when using yacc.
YYPRINT is a bison-ism so c_print_token() ends up being unused when yacc is
used which makes gcc unhappy. Make sure we only define YYPRINT and
c_print_token() when bison is used to generate the parser.
gdb/ChangeLog:
* c-exp.y (YYPRINT, c_print_token): Only define if YYBISON is
defined.
---
gdb/ChangeLog | 5 +++++
gdb/c-exp.y | 6 ++++++
2 files changed, 11 insertions(+)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a6fa6fc..fcec355 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2014-02-05 Mark Kettenis <kettenis@gnu.org>
+
+ * c-exp.y (YYPRINT, c_print_token): Only define if YYBISON is
+ defined.
+
2014-02-05 Yao Qi <yao@codesourcery.com>
* remote.c (remote_pass_signals): Remove local 'buf' and use
diff --git a/gdb/c-exp.y b/gdb/c-exp.y
index 277242e..4704845 100644
--- a/gdb/c-exp.y
+++ b/gdb/c-exp.y
@@ -169,8 +169,10 @@ static struct stoken operator_stoken (const char *);
static void check_parameter_typelist (VEC (type_ptr) *);
static void write_destructor_name (struct stoken);
+#ifdef YYBISON
static void c_print_token (FILE *file, int type, YYSTYPE value);
#define YYPRINT(FILE, TYPE, VALUE) c_print_token (FILE, TYPE, VALUE)
+#endif
%}
%type <voidval> exp exp1 type_exp start variable qualified_name lcurly
@@ -3201,6 +3203,8 @@ c_parse (void)
return result;
}
+#ifdef YYBISON
+
/* This is called via the YYPRINT macro when parser debugging is
enabled. It prints a token's value. */
@@ -3255,6 +3259,8 @@ c_print_token (FILE *file, int type, YYSTYPE value)
}
}
+#endif
+
void
yyerror (char *msg)
{
--
1.8.5.3
prev parent reply other threads:[~2014-02-05 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 13:51 Mark Kettenis
2014-02-05 2:13 ` Joel Brobecker
2014-02-05 12:37 ` Mark Kettenis [this message]
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=201402051237.s15CbhlK028161@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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: 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