From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/build] Fix missing implicit constructor call with gcc 4.8
Date: Sat, 8 Aug 2020 23:35:06 +0200 [thread overview]
Message-ID: <20200808213504.GA28308@delia> (raw)
Hi,
When building gdb on x86_64-linux with --enable-targets riscv64-suse-linux, I
run into:
...
src/gdb/arch/riscv.c:112:45: required from here
/usr/include/c++/4.8/bits/hashtable_policy.h:195:39: error: no matching \
function for call to 'std::pair<const riscv_gdbarch_features, const \
std::unique_ptr<target_desc, target_desc_deleter> >::pair(const \
riscv_gdbarch_features&, target_desc*&)'
: _M_v(std::forward<_Args>(__args)...) { }
^
...
for this code in riscv_lookup_target_description:
...
/* Add to the cache. */
riscv_tdesc_cache.emplace (features, tdesc);
...
Work around this compiler problem (filed as PR gcc/96537), similar to how that
was done in commit 6d0cf4464e "Fix build with gcc-4.8.x":
...
- riscv_tdesc_cache.emplace (features, tdesc);
+ riscv_tdesc_cache.emplace (features, target_desc_up (tdesc));
...
That is, call the target_desc_up constructor explictly instead of implicitly.
Also, work around a similar issue in get_thread_arch_aspace_regcache.
Build on x86_64-linux with --enable-targets riscv64-suse-linux, and
reg-tested.
Committed to trunk.
Thanks,
- Tom
[gdb/build] Fix missing implicit constructor call with gcc 4.8
gdb/ChangeLog:
2020-08-08 Tom de Vries <tdevries@suse.de>
PR build/26344
* arch/riscv.c (riscv_lookup_target_description): Use an explicit
constructor.
* regcache.c (get_thread_arch_aspace_regcache): Same.
---
gdb/arch/riscv.c | 5 +++--
gdb/regcache.c | 4 +++-
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/gdb/arch/riscv.c b/gdb/arch/riscv.c
index e43aafc1c2..8f5709092e 100644
--- a/gdb/arch/riscv.c
+++ b/gdb/arch/riscv.c
@@ -108,8 +108,9 @@ riscv_lookup_target_description (const struct riscv_gdbarch_features features)
target_desc *tdesc = riscv_create_target_description (features);
- /* Add to the cache. */
- riscv_tdesc_cache.emplace (features, tdesc);
+ /* Add to the cache. Work around a problem with g++ 4.8 (PR96537):
+ Call the target_desc_up constructor explictly instead of implicitly. */
+ riscv_tdesc_cache.emplace (features, target_desc_up (tdesc));
return tdesc;
}
diff --git a/gdb/regcache.c b/gdb/regcache.c
index b8fcc52860..cd54bc6b5f 100644
--- a/gdb/regcache.c
+++ b/gdb/regcache.c
@@ -354,7 +354,9 @@ get_thread_arch_aspace_regcache (process_stratum_target *target,
/* It does not exist, create it. */
regcache *new_regcache = new regcache (target, arch, aspace);
new_regcache->set_ptid (ptid);
- ptid_regc_map.insert (std::make_pair (ptid, new_regcache));
+ /* Work around a problem with g++ 4.8 (PR96537): Call the regcache_up
+ constructor explictly instead of implicitly. */
+ ptid_regc_map.insert (std::make_pair (ptid, regcache_up (new_regcache)));
return new_regcache;
}
reply other threads:[~2020-08-08 21:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200808213504.GA28308@delia \
--to=tdevries@suse.de \
--cc=gdb-patches@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