From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Fix build breaker with gcc 4.8
Date: Wed, 19 Jun 2019 14:35:00 -0000 [thread overview]
Message-ID: <41c82ba8-202b-f02d-178f-901d7d69c60d@suse.de> (raw)
In-Reply-To: <bdbbe02e-4dba-1a62-553b-80d206743e33@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On 19-06-19 14:43, Pedro Alves wrote:
> On 6/19/19 12:04 PM, Tom de Vries wrote:
>> Hi,
>>
>> When compiling with gcc 4.8, we run into:
>> ...
>> /usr/include/c++/4.8/bits/unordered_map.h:100:18: required from \
>> âclass std::unordered_map<sect_offset, std::vector<sect_offset> >â
>> src/gdb/dwarf2read.h:260:5: required from here
>> /usr/include/c++/4.8/bits/hashtable_policy.h:1070:12: error: invalid use of \
>> incomplete type âstruct std::hash<sect_offset>â
>> ...
>>
>> Fix this by adding std::hash<sect_offset>.
>>
>> Build and reg-tested on x86_64-linux with gcc 4.8.
>>
>> OK for trunk?
>>
>
> hash_enum was added for this:
>
> https://sourceware.org/ml/gdb-patches/2017-12/msg00210.html
>
> Can you use it here?
>
> It's currently used in dwarf2read.c, here:
>
> std::unordered_map<sect_offset,
> dwarf2_per_cu_data *,
> gdb::hash_enum<sect_offset>>
>
Yes, that works for me.
OK for trunk?
Thanks,
- Tom
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gdb-Fix-build-breaker-with-gcc-4.8.patch --]
[-- Type: text/x-patch; name="0001-gdb-Fix-build-breaker-with-gcc-4.8.patch", Size: 1633 bytes --]
[gdb] Fix build breaker with gcc 4.8
When compiling with gcc 4.8, we run into:
...
/usr/include/c++/4.8/bits/unordered_map.h:100:18: required from \
âclass std::unordered_map<sect_offset, std::vector<sect_offset> >â
src/gdb/dwarf2read.h:260:5: required from here
/usr/include/c++/4.8/bits/hashtable_policy.h:1070:12: error: invalid use of \
incomplete type âstruct std::hash<sect_offset>â
...
Fix this by setting the Hash template parameter of the unordered_map to
gdb::hash_enum<sect_offset>, rather than using the default
std::hash<sect_offset>.
Build and reg-tested on x86_64-linux with gcc 4.8.
gdb/ChangeLog:
2019-06-19 Tom de Vries <tdevries@suse.de>
* dwarf2read.h (abstract_to_concrete): Change type to
std::unordered_map<sect_offset, std::vector<sect_offset>,
gdb::hash_enum<sect_offset>>.
---
gdb/dwarf2read.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gdb/dwarf2read.h b/gdb/dwarf2read.h
index 776860e454..7113cfd384 100644
--- a/gdb/dwarf2read.h
+++ b/gdb/dwarf2read.h
@@ -24,6 +24,7 @@
#include "dwarf-index-cache.h"
#include "filename-seen-cache.h"
#include "gdb_obstack.h"
+#include "common/hash_enum.h"
/* Hold 'maintenance (set|show) dwarf' commands. */
extern struct cmd_list_element *set_dwarf_cmdlist;
@@ -256,7 +257,8 @@ public:
/* Mapping from abstract origin DIE to concrete DIEs that reference it as
DW_AT_abstract_origin. */
- std::unordered_map<sect_offset, std::vector<sect_offset>>
+ std::unordered_map<sect_offset, std::vector<sect_offset>, \
+ gdb::hash_enum<sect_offset>> \
abstract_to_concrete;
};
next prev parent reply other threads:[~2019-06-19 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 11:04 Tom de Vries
2019-06-19 12:43 ` Pedro Alves
2019-06-19 14:35 ` Tom de Vries [this message]
2019-06-19 14:49 ` Pedro Alves
2019-06-19 14:56 ` Steve Ellcey
[not found] ` <0cedb79e-1423-90d8-0c61-1386f398ab20@suse.de>
2019-06-19 15:14 ` [EXT] " Steve Ellcey
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=41c82ba8-202b-f02d-178f-901d7d69c60d@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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