From: Lancelot SIX <Lancelot.Six@amd.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/python/python-internal.h: avoid uninitialized constexpr
Date: Tue, 18 Jun 2024 19:27:04 +0100 [thread overview]
Message-ID: <2317caf4-6fdb-46d1-b2aa-caffed3faffe@amd.com> (raw)
In-Reply-To: <8734pacjju.fsf@tromey.com>
On 18/06/2024 17:17, Tom Tromey wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
>>>>>> "Lancelot" == Lancelot SIX <lancelot.six@amd.com> writes:
>
> Lancelot> template<typename T>
> Lancelot> -constexpr char gdbpy_method_format;
> Lancelot> +struct gdbpy_method_format {};
>
> Would it work to just remove the 'constexpr' from this line?
>
> Tom
Just gave a try to this approach, I end up linker errors regarding
duplicated symbols:
ld.lld: error: duplicate symbol: gdbpy_method_format<long long>
>>> defined at python-internal.h:154
(../../gdb/python/python-internal.h:154)
>>> python/py-arch.o:(gdbpy_method_format<long long>)
>>> defined at python-internal.h:154
(../../gdb/python/python-internal.h:154)
>>> python/py-auto-load.o:(.data+0x0)
ld.lld: error: duplicate symbol: gdbpy_method_format<unsigned long long>
>>> defined at python-internal.h:157
(../../gdb/python/python-internal.h:157)
>>> python/py-arch.o:(gdbpy_method_format<unsigned long long>)
>>> defined at python-internal.h:157
(../../gdb/python/python-internal.h:157)
>>> python/py-auto-load.o:(.data+0x20)
I have not really looked if there is a way to work-around that.
Best,
Lancelot.
next prev parent reply other threads:[~2024-06-18 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 9:09 Lancelot SIX
2024-06-18 13:00 ` Tom de Vries
2024-06-18 15:25 ` Tom de Vries
2024-06-18 16:17 ` Tom Tromey
2024-06-18 18:27 ` Lancelot SIX [this message]
2024-06-18 19:48 ` Tom Tromey
2024-06-18 21:01 ` Lancelot SIX
2024-06-18 21:03 ` Tom Tromey
2024-06-18 21:26 ` Lancelot SIX
2024-06-19 0:11 ` Tom Tromey
2024-06-19 9:16 ` Lancelot SIX
2024-06-19 13:41 ` Tom Tromey
2024-06-19 14:29 ` Lancelot SIX
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=2317caf4-6fdb-46d1-b2aa-caffed3faffe@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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