From: Tristan Gingold <gingold@adacore.com>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils <binutils@sourceware.org>
Subject: Re: Release 2.21 - Pre tests
Date: Wed, 24 Nov 2010 08:23:00 -0000 [thread overview]
Message-ID: <859274A2-4652-48A3-A447-72AB5F31574D@adacore.com> (raw)
In-Reply-To: <mcreiabu4zx.fsf@google.com>
On Nov 23, 2010, at 10:03 PM, Ian Lance Taylor wrote:
> Tristan Gingold <gingold@adacore.com> writes:
>
>> 2) I wasn't able to build gold with the compilers I used (gcc 4.1.2 from RH or gcc 4.1.0 from SUSE)
>
> What failed?
../../binutils-2.20.90/gold/arm.cc: In instantiation of 'const size_t <unnamed>::Target_arm<false>::fake_relnum_for_stubs':
../../binutils-2.20.90/gold/arm.cc:8627: instantiated from 'bool<unnamed>::Target_arm<big_endian>::Relocate::relocate(const gold::Relocate_info<32, big_endian>*, <unnamed>::Target_arm<big_endian>*, gold::Output_section*, size_t, const elfcpp::Rel<32, big_endian>&, unsigned int, const gold::Sized_symbol<32>*, const gold::Symbol_value<32>*, unsigned char*, <unnamed>::Arm_address, gold::section_size_type) [with bool big_endian = false]'
../../binutils-2.20.90/gold/target-reloc.h:334: instantiated from 'void gold::relocate_section(const gold::Relocate_info<size, big_endian>*, Target_type*, const unsigned char*, size_t, gold::Output_section*, bool, unsigned char*, typename elfcpp::Elf_types<size>::Elf_Addr, gold::section_size_type, const gold::Reloc_symbol_changes*) [with int size = 32, bool big_endian = false, Target_type = <unnamed>::Target_arm<false>, int sh_type = 9, Relocate = <unnamed>::Target_arm<false>::Relocate]'
../../binutils-2.20.90/gold/arm.cc:9263: instantiated from 'void<unnamed>::Target_arm<big_endian>::relocate_section(const gold::Relocate_info<32, big_endian>*, unsigned int, const unsigned char*, size_t, gold::Output_section*, bool, unsigned char*, <unnamed>::Arm_address, gold::section_size_type, const gold::Reloc_symbol_changes*) [with bool big_endian = false]'
../../binutils-2.20.90/gold/arm.cc:11770: instantiated from here
../../binutils-2.20.90/gold/arm.cc:2140: internal compiler error: in make_rtl_for_nonlocal_decl, at cp/decl.c:5067
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/ccEtfk5w.out file, please attach this to your bugreport.
or (on SUSE):
../../binutils-2.20.90/gold/icf.cc: In function ‘bool gold::match_sections(unsigned int, gold::Symbol_table*, std::vector<unsigned int, std::allocator<unsigned int> >*, std::vector<unsigned int, std::allocator<unsigned int> >*, const std::vector<std::pair<gold::Object*, unsigned int>, std::allocator<std::pair<gold::Object*, unsigned int> > >&, std::vector<bool, std::allocator<bool> >*, std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*)’:
../../binutils-2.20.90/gold/icf.cc:616: error: no matching function for call to ‘Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator()’
/usr/include/c++/4.1.0/tr1/hashtable:309: note: candidates are: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:305: note: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>*, Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:295: note: Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator(const Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>&)
/usr/include/c++/4.1.0/bits/stl_pair.h: In constructor ‘std::pair<_T1, _T2>::pair() [with _T1 = Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>, _T2 = bool]’:
../../binutils-2.20.90/gold/icf.cc:173: instantiated from here
/usr/include/c++/4.1.0/bits/stl_pair.h:81: error: no matching function for call to ‘Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator()’
/usr/include/c++/4.1.0/tr1/hashtable:309: note: candidates are: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:305: note: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>*, Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:295: note: Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator(const Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>&)
/usr/include/c++/4.1.0/bits/stl_pair.h: In constructor ‘std::pair<_T1, _T2>::pair() [with _T1 = Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>, _T2 = Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>]’:
../../binutils-2.20.90/gold/icf.cc:552: instantiated from here
/usr/include/c++/4.1.0/bits/stl_pair.h:81: error: no matching function for call to ‘Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator()’
/usr/include/c++/4.1.0/tr1/hashtable:309: note: candidates are: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:305: note: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>*, Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:295: note: Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator(const Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>&)
/usr/include/c++/4.1.0/bits/stl_pair.h:81: error: no matching function for call to ‘Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator()’
/usr/include/c++/4.1.0/tr1/hashtable:309: note: candidates are: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:305: note: Internal::hashtable_iterator<Value, constant_iterators, cache>::hashtable_iterator(Internal::hash_node<Value, cache>*, Internal::hash_node<Value, cache>**) [with Value = std::pair<const unsigned int, unsigned int>, bool constant_iterators = false, bool cache = false]
/usr/include/c++/4.1.0/tr1/hashtable:295: note: Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>::hashtable_iterator(const Internal::hashtable_iterator<std::pair<const unsigned int, unsigned int>, false, false>&)
Tristan.
next prev parent reply other threads:[~2010-11-24 8:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 11:45 Release 2.21 (ready ?) Tristan Gingold
2010-11-19 16:11 ` Doug Kwan (關振德)
2010-11-20 0:02 ` Ian Lance Taylor
2010-11-19 17:10 ` Joel Sherrill
2010-11-23 16:32 ` Release 2.21 - Pre tests Tristan Gingold
2010-11-23 18:54 ` Matthias Klose
2010-11-24 9:28 ` Richard Sandiford
2010-11-24 14:40 ` Matthew Gretton-Dann
2010-11-25 1:40 ` Alan Modra
2010-11-25 9:49 ` Matthew Gretton-Dann
2010-11-25 9:55 ` Tristan Gingold
2010-11-25 15:16 ` Matthew Gretton-Dann
2010-11-23 21:04 ` Ian Lance Taylor
2010-11-23 21:17 ` H.J. Lu
2010-11-23 23:00 ` Ian Lance Taylor
2010-11-23 23:09 ` H.J. Lu
2010-11-24 8:23 ` Tristan Gingold [this message]
2010-12-01 0:21 ` Ian Lance Taylor
2010-12-01 11:03 ` Tristan Gingold
2010-12-01 16:53 ` Ian Lance Taylor
2010-12-08 10:47 ` Tristan Gingold
2010-12-08 15:55 ` Ian Lance Taylor
2010-12-08 16:02 ` Tristan Gingold
2010-11-24 9:53 ` Matthew Gretton-Dann
2010-11-24 9:56 ` Tristan Gingold
2010-12-01 15:14 ` Release 2.21 - Soon Tristan Gingold
2010-12-01 15:18 ` H.J. Lu
2010-12-02 15:03 ` Tristan Gingold
2010-12-03 17:43 ` Steve Ellcey
2010-12-03 18:08 ` Maciej W. Rozycki
2010-12-03 18:26 ` Steve Ellcey
2010-12-04 0:44 ` Maciej W. Rozycki
2010-12-03 21:11 ` Steve Ellcey
2010-12-04 0:55 ` Maciej W. Rozycki
2010-12-06 10:46 ` Chris Smith
2010-12-06 14:02 ` Tristan Gingold
2010-12-06 16:36 ` Steve Ellcey
2010-12-06 17:35 ` Maciej W. Rozycki
2010-12-06 17:40 ` H.J. Lu
2010-12-07 8:24 ` Tristan Gingold
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=859274A2-4652-48A3-A447-72AB5F31574D@adacore.com \
--to=gingold@adacore.com \
--cc=binutils@sourceware.org \
--cc=iant@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).