public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30174] Rework 'main' name yet again Date: Sun, 06 Aug 2023 22:22:21 +0000 [thread overview] Message-ID: <bug-30174-4717-RHpc5NwwA2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30174-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30174 --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom Tromey from comment #4) > > I build the branch (I had to build with gcc-12, I ran into a build breaker > > with gcc-7) > > What was that? This one: ... In file included from /data/vries/gdb/src/gdb/dwarf2/cooked-index.h:39:0, from /data/vries/gdb/src/gdb/dwarf2/cooked-index.c:21: /data/vries/gdb/src/gdb/../gdbsupport/task-group.h:90:34: error: use of deleted function ‘std::ato\ mic<int>::atomic(const std::atomic<int>&)’ std::atomic<int> m_completed = 0; ^ In file included from /usr/include/c++/7/future:42:0, from /data/vries/gdb/src/gdb/../gdbsupport/thread-pool.h:31, from /data/vries/gdb/src/gdb/dwarf2/cooked-index.h:33, from /data/vries/gdb/src/gdb/dwarf2/cooked-index.c:21: /usr/include/c++/7/atomic:668:7: note: declared here atomic(const atomic&) = delete; ^~~~~~ /usr/include/c++/7/atomic:672:17: note: after user-defined conversion: constexpr std::atomic<int\ >::atomic(std::atomic<int>::__integral_type) constexpr atomic(__integral_type __i) noexcept : __base_type(__i) { } ^~~~~~ ... and two more like it. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-06 22:22 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-26 16:33 [Bug symtab/30174] New: " tromey at sourceware dot org 2023-02-26 16:33 ` [Bug symtab/30174] " tromey at sourceware dot org 2023-02-26 16:34 ` tromey at sourceware dot org 2023-08-04 17:19 ` tromey at sourceware dot org 2023-08-05 8:56 ` vries at gcc dot gnu.org 2023-08-05 14:00 ` vries at gcc dot gnu.org 2023-08-06 15:03 ` tromey at sourceware dot org 2023-08-06 22:22 ` vries at gcc dot gnu.org [this message] 2023-10-24 19:40 ` tromey at sourceware dot org 2023-10-25 8:43 ` sam at gentoo dot org 2023-11-12 23:27 ` tromey at sourceware dot org 2024-01-09 1:46 ` cvs-commit at gcc dot gnu.org 2024-01-09 1:49 ` tromey at sourceware dot 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-30174-4717-RHpc5NwwA2@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: linkBe 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).