public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tes.vik1986 at gmail dot com" <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: Sun, 26 Sep 2021 13:31:38 +0000 [thread overview]
Message-ID: <bug-27385-4717-ZW2em9Jm2W@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27385-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27385
Kylan <tes.vik1986 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tes.vik1986 at gmail dot com
--- Comment #12 from Kylan <tes.vik1986 at gmail dot com> ---
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,
https://komiya-dental.com/technology/miui-13/
from /usr/include/c++/4.8.2/tuple:38,
from /usr/include/c++/4.8.2/functional:55,
http://www-look-4.com/technology/peugeot-208/
from ../../gdb/../gdbsupport/ptid.h:35,
from ../../gdb/../gdbsupport/common-defs.h:123,
http://www.iu-bloomington.com/technology/miui13/
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
https://www.webb-dev.co.uk/technology/grt-r910/
..._Indexes2> std::pair<_T1, _T2>::pair(std::tuple<_Args1 ...>&,
https://waytowhatsnext.com/technology/korean-technology/
std::tuple<_Args2 ...>&, std::_Index_tuple<_Indexes1 ...>,
std::_Index_tuple<_Indexes2 ...>)
http://www.acpirateradio.co.uk/travel/carbon-dioxide-emissions/
pair(tuple<_Args1...>&, tuple<_Args2...>&,
http://www.logoarts.co.uk/travel/actions-camera/
^
-------->8---------
http://www.slipstone.co.uk/travel/hyundai-kona/
The corresponding line in arc.c must use an explicit ctor:
--------8<--------- http://embermanchester.uk/travel/whatsapp/
arc_lookup_target_description (...)
{
http://connstr.net/travel/charging-machines/
/* Add the newly created target description to the repertoire. */
- arc_tdesc_cache.emplace (features, tdesc);
+ arc_tdesc_cache.emplace (features, target_desc_up (tdesc));
http://joerg.li/category/technology/
return tdesc;
} http://www.compilatori.com/travel/youtube/
-------->8---------
See "PR gcc/96537" for more details.
http://www.jopspeech.com/category/technology/
Last but not least, this problem has originally been investigated
by Tom de Vries for RISCV targets (see 38f8aa06d9). arc: Fix gcc-4.8
compilation failure for arc.c
http://www.wearelondonmade.com/category/technology/
Building an arc target:
$ configulre --target=arc-elf32 \
--enable-targets=arc-linux-uclibc \
...
https://ground-cover.mx/
https://marijuana-netting.net/
https://gallinero.mx/
https://control-de-palomas.mx/
https://shade-cloth.net/
https://trellis-netting.net/
https://invernavelo.net/
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
http://frost-fabric.net/
http://gancho-tutoreo-tenax.net/
http://flower-supports.net/
http://hail-protection-net.com/
https://www.hortomallas.net/
http://macro-tunel.com/
https://scrog.mx/
https://cannabis-netting.net/
https://casa-sombra.mx/
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,
https://fintechzoom.com/lifestyle/entertainment/gaming/zombie-games-do-you-know-what-are-the-best-games-for-pc-in-2021/
https://fintechzoom.com/lifestyle/entertainment/gaming/final-fantasy/ffxiv-classes-guide-on-final-fantasy-14-select-the-best-job/
https://www.cinogel.com/
https://mohamie-saudi.com/
https://fintechzoom.com/lifestyle/entertainment/gaming/rimworld/the-best-rimworld-mods/
https://www.nimblehand.com/
https://www.hortomallas.com/en/product-category/privacy-and-windbreakers/polisombra-total-privacy/
https://www.hortomallas.com/en/grow-pumpkin-on-trellises-netting/
https://www.hortomallas.com/malla-plastica-para-jardin-canceles-vallas-rejas/
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 ...>) https://guacamalla.net/
https://hortomallas.es/
https://malla-espaldera.mx/
https://malla-pepinera.com/
https://malla-sombra.mx/
https://manta-termica.com/
https://www.hortomallas.com/en/best-price-of-the-chicken-netting-save-money-with-chickenmalla/
https://www.hortomallas.com/en/tomato-cages/
https://www.mindrnd.com/
https://akoestiekopmaat.nl/
pair(tuple<_Args1...>&, tuple<_Args2...>&,
^
-------->8---------
The corresponding line in arc.c must use an explicit ctor:
--------8<---------
arc_lookup_target_description (...) https://rattanmart.com/
https://bohemiansmart.com/
https://mohamie-jeddah.com/
https://www.beyandiet.com/
https://www.bebealis.com/
https://byothe.fr/
https://ns-communication.fr/
https://www.hortomallas.com/en/the-advantage-of-chicken-wire-mesh-with-hexagonal-netting/
https://www.hortomallas.com/en/how-tall-should-the-cucumber-trellis-height-be/
https://www.hortomallas.com/precio-la-tela-gallinera-bajo/
{
/* 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.
https://geoslam.xyz/
https://fintechzoom.com/lifestyle/entertainment/gaming/tower-defense-simulator/codes/
https://www.lafabriquedeslutins.fr/
https://www.station-alexandre.com/
https://fintechzoom.com/lifestyle/entertainment/gaming/ro-ghoul/roblox-ro-ghoul-codes/
https://www.hunny-pool.com/
https://www.formations-continues.com/
https://nutrienta.co/
https://2macp.fr/
https://mymystore.online/
https://www.antiguachiamaitalia.it/
Last but not least, this problem has originally been investigated
(see 38f8aa06d9).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-26 13:31 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
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 [this message]
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-ZW2em9Jm2W@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).