From: Tom de Vries <tdevries@suse.de>
To: Sam James <sam@gentoo.org>, gdb-patches@sourceware.org
Cc: Tom de Vries <vries@gcc.gnu.org>
Subject: Re: [PATCH] gdb: Fix an ODR warning with byacc with GDB_YY_REMAP
Date: Tue, 12 Sep 2023 12:49:14 +0200 [thread overview]
Message-ID: <02ec4de4-8bad-4ab1-a72e-6d45244927a8@suse.de> (raw)
In-Reply-To: <20230912010238.3086346-1-sam@gentoo.org>
On 9/12/23 02:58, Sam James wrote:
> With byacc, we get an ODR warning with YYSTACKDATA between ada-exp.c.tmp
> and c-exp.c.tmp. Just include it in the list of symbols we rename.
>
> PR gdb/30839
>
Please make that "PR build/30839".
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30839
> Acked-by: Tom de Vries <vries@gcc.gnu.org>
Please change that to "Approved-By: Tom de Vries <tdevries@suse.de>"
(note the difference in email address).
Otherwise LGTM, please commit.
> Signed-off-by: Sam James <sam@gentoo.org>
> ---
>
> Few notes:
> - Tom commented that it probably constitutes obvious but while I have binutils
> access, I'm not listed in gdb/MAINTAINERS for write-after-approval, so I'm
> hesitant.
>
> - The top of yy-remap.h does mention that we should fix yacc impls which emit
> symbols that clash that aren't in the list, but meh. I'm not sure we've even
> stuck to that rule for the other symbols, and the list is already for non-Bison
> anyway...
>
[ Yeah, I think it would be more useful to divide up the list, and
reformulate the comment as "list below needs to be fixed in
corresponding parser generators" or some such.
Let's not bother with that for this commit though. ]
Thanks,
- Tom
> gdb/yy-remap.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/gdb/yy-remap.h b/gdb/yy-remap.h
> index 33bee0fabdb..d0125b9ed45 100644
> --- a/gdb/yy-remap.h
> +++ b/gdb/yy-remap.h
> @@ -85,6 +85,7 @@
> #define yystacksize GDB_YY_REMAP (yystacksize)
> #define yyvs GDB_YY_REMAP (yyvs)
> #define yyvsp GDB_YY_REMAP (yyvsp)
> +#define YYSTACKDATA GDB_YY_REMAP (YYSTACKDATA)
>
> /* The following are common to all parsers. */
>
next prev parent reply other threads:[~2023-09-12 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 0:58 Sam James
2023-09-12 10:49 ` Tom de Vries [this message]
2023-09-12 13:03 ` Tom de Vries
2023-09-26 13:48 ` Tom Tromey
2023-09-26 13:57 ` Tom de Vries
2023-09-27 7:35 ` Sam James
2023-09-27 7:52 ` Tom de Vries
2023-09-28 2:56 ` Sam James
2023-09-28 8:30 ` Tom de Vries
2023-09-29 4:37 ` Sam James
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=02ec4de4-8bad-4ab1-a72e-6d45244927a8@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=sam@gentoo.org \
--cc=vries@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).