public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/32503] gdb: 'construct' has not been declared in 'std::allocator<unsigned char>
Date: Fri, 10 Jan 2025 07:40:27 +0000	[thread overview]
Message-ID: <bug-32503-4717-19tzSvGgOe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-32503-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=32503

--- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6f04937e1d7db190ca96ec08d8aeb25f0ec6e994

commit 6f04937e1d7db190ca96ec08d8aeb25f0ec6e994
Author: Tom de Vries <tdevries@suse.de>
Date:   Fri Jan 10 08:40:11 2025 +0100

    [gdb/build, c++20] Fix build with gcc 10

    With gcc 10 and -std=c++20, we run into the same problem as reported in
commit
    6feae66da1d ("[gdb/build, c++20] Handle deprecated
std::allocator::construct").

    The problem was fixed using:
    ...
    -template<typename T, typename A = std::allocator<T>>
    +template<typename T,
    +         typename A
    +#if __cplusplus >= 202002L
    +         = std::pmr::polymorphic_allocator<T>
    +#else
    +         = std::allocator<T>
    +#endif
    +        >
    ...
    but that doesn't work for gcc 10, because it defines __cplusplus
differently:
    ...
     $ echo | g++-10 -E -dD -x c++ - -std=c++20 2>&1 | grep __cplusplus
     #define __cplusplus 201709L
     $ echo | g++-11 -E -dD -x c++ - -std=c++20 2>&1 | grep __cplusplus
     #define __cplusplus 202002L
    ...

    Fix this by using the library feature test macro
    __cpp_lib_polymorphic_allocator [1], which is undefined for c++17 and
defined
    for c++20:
    ...
     $ echo | g++-10 -E -dD -x c++ - -include memory_resource -std=c++17 2>&1 \
       | grep __cpp_lib_polymorphic_allocator
     $ echo | g++-10 -E -dD -x c++ - -include memory_resource -std=c++20 2>&1 \
       | grep __cpp_lib_polymorphic_allocator
     #define __cpp_lib_polymorphic_allocator 201902L
     $
    ...

    A similar problem exists for commit 3173529d7de ("[gdb/guile, c++20] Work
    around Werror=volatile in libguile.h").  Fix this by testing for 201709L
    instead.

    Tested on x86_64-linux, by building gdb with
    {gcc 10, clang 17.0.6} x {-std=c++17, -std=c++20}.

    PR build/32503
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32503

    Approved-By: Tom Tromey <tom@tromey.com>

    [1]
https://en.cppreference.com/w/cpp/feature_test#cpp_lib_polymorphic_allocator

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2025-01-10  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27  3:52 [Bug gdb/32503] New: " jeffrey.cliff at gmail dot com
2024-12-27 11:35 ` [Bug gdb/32503] " ssbssa at sourceware dot org
2025-01-06 16:34 ` tromey at sourceware dot org
2025-01-07  7:45 ` [Bug build/32503] " vries at gcc dot gnu.org
2025-01-07  8:55 ` vries at gcc dot gnu.org
2025-01-10  7:40 ` cvs-commit at gcc dot gnu.org [this message]
2025-01-10  7:41 ` vries at gcc dot gnu.org

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=bug-32503-4717-19tzSvGgOe@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).