From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Fix build failure on macOS
Date: Wed, 18 Dec 2019 15:05:00 -0000 [thread overview]
Message-ID: <20191218150518.8540-1-tromey@adacore.com> (raw)
PR build/25250 notes that the gdb 9 pre-release fails to build on
macOS, due to a name clash between field_kind::STRING and the STRING
token in ada-exp.y. I am not sure (I couldn't reproduce this myself),
but presumably this is due to differences caused by the version of
bison in use there.
This patch works around the problem by renaming the field_kind
enumerator. I chose to rename this one because it is used in
relatively few places -- it's just an implementation detail of the
style code.
Let me know what you think. I intend to check this in on the gdb 9
branch as well.
gdb/ChangeLog
2019-12-18 Tom Tromey <tromey@adacore.com>
PR build/25250:
* ui-out.c (ui_out::vmessage): Update.
* ui-out.h (enum class) <FIELD_STRING>: Rename from STRING.
(string_field): Update.
Change-Id: Iae9f36f1b793e22c61fee0de2ab2d508668ee7e4
---
gdb/ChangeLog | 7 +++++++
gdb/ui-out.c | 2 +-
gdb/ui-out.h | 6 ++++--
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/gdb/ui-out.c b/gdb/ui-out.c
index 80845f4bcaa..6572546f26c 100644
--- a/gdb/ui-out.c
+++ b/gdb/ui-out.c
@@ -736,7 +736,7 @@ ui_out::vmessage (const ui_file_style &in_style, const char *format,
field_signed (f->name, f->val);
}
break;
- case field_kind::STRING:
+ case field_kind::FIELD_STRING:
{
auto *f = (string_field_s *) bf;
field_string (f->name, f->str);
diff --git a/gdb/ui-out.h b/gdb/ui-out.h
index 5c96a7825be..0bdb6b8b7d5 100644
--- a/gdb/ui-out.h
+++ b/gdb/ui-out.h
@@ -78,7 +78,9 @@ enum ui_out_type
enum class field_kind
{
SIGNED,
- STRING,
+ /* This has a funny name to avoid clashes with tokens named
+ "STRING". See PR build/25250. */
+ FIELD_STRING,
};
/* The base type of all fields that can be emitted using %pF. */
@@ -126,7 +128,7 @@ string_field (const char *name, const char *str,
string_field_s &&tmp = {})
{
tmp.name = name;
- tmp.kind = field_kind::STRING;
+ tmp.kind = field_kind::FIELD_STRING;
tmp.str = str;
return &tmp;
}
--
2.21.0
next reply other threads:[~2019-12-18 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 15:05 Tom Tromey [this message]
2019-12-18 16:21 ` Pedro Alves
2019-12-18 16:35 ` Tom Tromey
2019-12-18 16:38 ` Pedro Alves
2019-12-18 19:18 ` Christian Biesinger via gdb-patches
2019-12-19 18:11 ` Tom Tromey
2019-12-18 16:32 ` Simon Marchi
2019-12-18 16:37 ` Tom Tromey
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=20191218150518.8540-1-tromey@adacore.com \
--to=tromey@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