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/27385] Cannot compile arc.c with gcc-4.8 (error: no matching function for call to 'std::pair...')
Date: Tue, 09 Feb 2021 17:38:39 +0000	[thread overview]
Message-ID: <bug-27385-4717-bLCksYGZrp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27385-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-10-branch branch has been updated by Shahab Vahedi
<shahab@sourceware.org>:

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

commit 15e1376fea4801f9bb9d5cacb0e6abc35693baa6
Author: Shahab Vahedi <shahab@synopsys.com>
Date:   Tue Feb 9 09:42:50 2021 +0100

    arc: Fix gcc-4.8 compilation failure for arc.c

    Building an arc target:

    $ configulre --target=arc-elf32                \
                 --enable-targets=arc-linux-uclibc \
                 ...

    On a system with gcc-4.8 (CentOS 7.x), fails with:
    --------8<---------
    ../../gdb/arch/arc.c:117:43:   required from here
    /usr/include/c++/4.8.2/bits/hashtable_policy.h:195:39: error: no matching
    function for call to 'std::pair<const arc_arch_features, const
    std::unique_ptr<target_desc, target_desc_deleter> >::pair(const
    arc_arch_features&, target_desc*&)'
      : _M_v(std::forward<_Args>(__args)...) { }
                                           ^
    /usr/include/c++/4.8.2/bits/hashtable_policy.h:195:39: note: candidates
are:
    In file included from /usr/include/c++/4.8.2/utility:70:0,
                     from /usr/include/c++/4.8.2/tuple:38,
                     from /usr/include/c++/4.8.2/functional:55,
                     from ../../gdb/../gdbsupport/ptid.h:35,
                     from ../../gdb/../gdbsupport/common-defs.h:123,
                     from ../../gdb/arch/arc.c:19:
    /usr/include/c++/4.8.2/bits/stl_pair.h:206:9: note: template<class ...
    _Args1, long unsigned int ..._Indexes1, class ... _Args2, long unsigned int
    ..._Indexes2> std::pair<_T1, _T2>::pair(std::tuple<_Args1 ...>&,
    std::tuple<_Args2 ...>&, std::_Index_tuple<_Indexes1 ...>,
    std::_Index_tuple<_Indexes2 ...>)
             pair(tuple<_Args1...>&, tuple<_Args2...>&,
             ^
    -------->8---------

    The corresponding line in arc.c must use an explicit ctor:
    --------8<---------
     arc_lookup_target_description (...)
     {

       /* Add the newly created target description to the repertoire.  */
    -  arc_tdesc_cache.emplace (features, tdesc);
    +  arc_tdesc_cache.emplace (features, target_desc_up (tdesc));

       return tdesc;
     }
    -------->8---------
    See "PR gcc/96537" for more details.

    Last but not least, this problem has originally been investigated
    by Tom de Vries for RISCV targets (see 38f8aa06d9).

    gdb/ChangeLog:

            PR build/27385
            * arch/arc.c (arc_lookup_target_description): Use
            target_desc_up() ctor explicitly.

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

  parent reply	other threads:[~2021-02-09 17:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  8:30 [Bug build/27385] New: " shahab.vahedi at gmail dot com
2021-02-09  8:30 ` [Bug build/27385] " shahab.vahedi at gmail dot com
2021-02-09  8:46 ` vries at gcc dot gnu.org
2021-02-09 17:38 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-09 22:10 ` shahab.vahedi at gmail dot com
2021-06-27 17:58 ` ahmedsayeed1982 at yahoo dot com
2021-08-19  6:02 ` ucelsanicin at yahoo dot com
2021-08-27 18:00 ` ribevi6798 at enamelme dot com
2021-09-06  9:09 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:40 ` mehmetgelisin at aol dot com
2021-09-14  1:33 ` jadinvestments1 at gmail dot com
2021-09-14 17:29 ` johnb6174 at gmail dot com
2021-09-14 18:49 ` mark at klomp dot org
2021-09-25  1:22 ` jadinvestments1 at gmail dot com
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-05 16:00 ` schaumburgkitchens at gmail dot com
2021-10-06 23:04 ` prosperousfish at gmail dot com
2021-10-08  4:09 ` johwelvic.bacolod at gmail dot com
2021-10-09 11:01 ` gulsenenginar at aol dot com
2021-10-10 16:11 ` oficaj3 at gmail dot com
2021-10-18 19:57 ` ahmedsayeed1982 at hotmail dot com
2021-10-19  7:14 ` progonsaytu at gmail dot com
2021-10-23 13:46 ` fiteva5725 at bomoads dot com
2021-10-24 10:01 ` glassmtech at ukr dot net
2021-11-02 15:22 ` gepaw63633 at dukeoo dot com
2021-11-06 21:12 ` paneki8601 at dukeoo dot com
2021-11-16 19:04 ` xecana8007 at funboxcn dot com
2021-11-16 19:08 ` xecana8007 at funboxcn dot com
2021-11-16 19:12 ` xecana8007 at funboxcn dot com
2021-11-16 19:16 ` xecana8007 at funboxcn dot com
2021-11-22  7:38 ` gexed96894 at keagenan dot com
2021-11-23  4:46 ` thebestdressedog at gmail dot com
2021-11-23  7:08 ` allen at rockvalleymarketing dot com
2021-11-23  9:00 ` joy at rockvalleymarketing dot com

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-27385-4717-bLCksYGZrp@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).