Re: [PATCH] gdb/python/python-internal.h: avoid uninitialized constexpr

[Lancelot SIX <Lancelot.Six@amd.com>]

On 18/06/2024 22:03, 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:
> 
>>> I think s/constexpr/extern probably works.
> 
> Lancelot> G++ complains that "explicit template specialization cannot have a
> Lancelot> storage class":
> 
> I meant just the constexpr on the "base case", not:
> 
> Lancelot>   154 | extern char gdbpy_method_format<gdb_py_longest> = GDB_PY_LL_ARG[0];
> 
> ... this one -- these have to be constexpr.
> 
> Tom

Oh, sorry, that makes more sense.

That works with GCC, but still fails with Clang.  I still have 
duplicate symbol errors (both at -O0 and -O3).  My understanding is that 
the compiler can still handle constexr as const if it wants, so marking 
those symbols constexpr will not necessarily prevent them from being 
materialized in the binary.

Lancelot.