Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@marvell.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       "tdevries@suse.de" <tdevries@suse.de>
Subject: Re: [PATCH][gdb] Fix build breaker with gcc 4.8
Date: Wed, 19 Jun 2019 14:56:00 -0000	[thread overview]
Message-ID: <0c2e64928ca6b526349f10ca073023fd50449f7f.camel@marvell.com> (raw)
In-Reply-To: <20190619110410.GA14131@delia>

On Wed, 2019-06-19 at 13:04 +0200, Tom de Vries wrote:
> 
> [gdb] Fix build breaker with gcc 4.8
> 
> gdb/ChangeLog:
> 
> 2019-06-19  Tom de Vries  <tdevries@suse.de>
> 
> 	* dwarf2read.h (std::hash<sect_offset>): New specialization.

I think this might have broken the GDB build with GCC 5.4.  My
gdb/binutils build using the latest sources is dying with the
following message.  I am building on Ubuntu 18.04 and the installed GCC
5.4 compiler.  I haven't seen any errors from the buildbot, maybe that
is using GCC 4.8?

Error:


In file included from /usr/include/c++/5/bits/hashtable.h:35:0,
                 from /usr/include/c++/5/unordered_map:47,
                 from /home/sellcey/tot/src/binutils-
gdb/gdb/dwarf2read.h:23,
                 from /home/sellcey/tot/src/binutils-gdb/gdb/dwarf-
index-write.h:24,
                 from /home/sellcey/tot/src/binutils-gdb/gdb/dwarf-
index-cache.c:28:
/usr/include/c++/5/bits/hashtable_policy.h: In instantiation of ‘struct
std::__detail::__is_noexcept_hash<sect_offset, std::hash<sect_offset>
>’:
/usr/include/c++/5/type_traits:137:12:   required from ‘struct
std::__and_<std::__is_fast_hash<std::hash<sect_offset> >,
std::__detail::__is_noexcept_hash<sect_offset, std::hash<sect_offset> >
>’
/usr/include/c++/5/type_traits:148:38:   required from ‘struct
std::__not_<std::__and_<std::__is_fast_hash<std::hash<sect_offset> >,
std::__detail::__is_noexcept_hash<sect_offset, std::hash<sect_offset> >
> >’

(etc, etc, etc)

  parent reply	other threads:[~2019-06-19 14:56 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
2019-06-19 14:49     ` Pedro Alves
2019-06-19 14:56 ` Steve Ellcey [this message]
     [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=0c2e64928ca6b526349f10ca073023fd50449f7f.camel@marvell.com \
    --to=sellcey@marvell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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