From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Mike Hommey <mhommey@mozilla.com>
Cc: Jan Hubicka <hubicka@ucw.cz>,
Xinliang David Li <davidxl@google.com>,
gcc@gcc.gnu.org, tglek@mozilla.com, dougkwan@google.com,
jingyu@google.com, Carrot Wei <carrot@google.com>,
Mark Heffernan <meheff@google.com>
Subject: Re: FDO and LTO on ARM
Date: Tue, 09 Aug 2011 13:04:00 -0000 [thread overview]
Message-ID: <CAH6eHdS9X9Lmr7un0zpxDCT-5VBR-xkJHjSfzVy0CsP30ja_cw@mail.gmail.com> (raw)
In-Reply-To: <20110809125707.GA9008@glandium.org>
On 9 August 2011 13:57, Mike Hommey wrote:
> On Mon, Aug 08, 2011 at 05:25:23PM +0100, Jonathan Wakely wrote:
>> On 8 August 2011 13:20, Mike Hommey wrote:
>> >
>> > I unfortunately hit several problems with gcc 4.7 (latest snapshot).
>> > One is bug 50022 that I filed today.
>> >
>> > Another is the following error in stlport headers:
>> > error: invalid use of incomplete type 'std::string {aka struct
>> > std::basic_string<char, std::char_traits<char>, std::allocator<char> >}'
>> >
>> > I also tried GNU libstdc++ instead of stlport but I hit some other
>> > errors that boil down to the following:
>> > error: 'std::wstring' has not been declared
>>
>> They both look as though they could be caused by something as simple
>> as failing to include <string> rather than a problem in GCC. Could
>> you send me more context for the errors (offlist if you prefer)? I'll
>> see if it's something we've changed in libstdc++, though given that
>> STlport fails too it seems unlikely.
>
> I identified the libstdc++ failure as a problem when building gcc:
>
> configure:16321: /tmp/build-ndk/gcc-4.7.0/./gcc/xgcc -shared-libgcc -B/tmp/build-ndk/gcc-4.7.0/./gcc -nostdinc++ -L/tmp/build-ndk/gcc-4.7.0/arm-linux-androideabi/libstdc++-v3/src -L/tmp/build-ndk/gcc-4.7.0/arm-linux-androideabi/libstdc++-v3/src/.libs -B/tmp/android-ndk-r6/toolchains/arm-linux-androideabi-4.7.0/prebuilt/linux-x86/arm-linux-androideabi/bin/ -B/tmp/android-ndk-r6/toolchains/arm-linux-androideabi-4.7.0/prebuilt/linux-x86/arm-linux-androideabi/lib/ -isystem /tmp/android-ndk-r6/toolchains/arm-linux-androideabi-4.7.0/prebuilt/linux-x86/arm-linux-androideabi/include -isystem /tmp/android-ndk-r6/toolchains/arm-linux-androideabi-4.7.0/prebuilt/linux-x86/arm-linux-androideabi/sys-include -c -frtti -fexceptions -O2 -Os -g -DTARGET_POSIX_IO -fno-short-enums conftest.cpp >&5
> conftest.cpp:35:18: error: 'INT_MIN' was not declared in this scope
> conftest.cpp:36:18: error: 'INT_MAX' was not declared in this scope
> (snip)
> configure:16345: checking for enabled wchar_t specializations
> configure:16347: result: no
>
> Thus _GLIBCXX_USE_WCHAR_T is not defined, and as such, the typedef
> for wstring isn't either.
Ah ok - that happens when the C library doesn't provide all the
required wchar_t functions, fwprintf, mbrtowc etc.
next prev parent reply other threads:[~2011-08-09 13:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 14:05 Mike Hommey
2011-08-04 15:16 ` Richard Guenther
2011-08-04 16:38 ` Mike Hommey
2011-08-04 18:42 ` Jan Hubicka
2011-08-05 7:32 ` Richard Guenther
2011-08-05 14:40 ` Jan Hubicka
2011-08-05 17:39 ` Xinliang David Li
2011-08-05 17:50 ` Xinliang David Li
2011-08-08 9:26 ` Mike Hommey
2011-08-08 12:16 ` Mike Hommey
2011-08-04 17:02 ` Xinliang David Li
2011-08-04 17:16 ` Denis Chertykov
2011-08-04 18:51 ` Jan Hubicka
2011-08-08 12:21 ` Mike Hommey
2011-08-08 16:25 ` Jonathan Wakely
2011-08-09 12:57 ` Mike Hommey
2011-08-09 13:04 ` Jonathan Wakely [this message]
2011-08-09 23:35 ` Fu, Chao-Ying
2011-08-09 13:21 ` Mike Hommey
2011-08-09 17:40 ` Marc Glisse
2011-08-09 18:11 ` Mike Hommey
2011-08-11 14:22 ` Mike Hommey
2011-08-11 16:27 ` Xinliang David Li
2011-08-17 15:35 ` Mike Hommey
2011-08-17 17:22 ` Xinliang David Li
2011-08-17 17:33 ` Mike Hommey
2011-08-05 19:49 Jan Hubicka
2011-08-05 21:34 ` Xinliang David Li
2011-08-05 22:25 ` Jan Hubicka
2011-08-08 20:03 ` Xinliang David Li
2011-08-08 20:36 ` Jan Hubicka
2011-08-11 13:51 ` Richard Earnshaw
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=CAH6eHdS9X9Lmr7un0zpxDCT-5VBR-xkJHjSfzVy0CsP30ja_cw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=carrot@google.com \
--cc=davidxl@google.com \
--cc=dougkwan@google.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jingyu@google.com \
--cc=meheff@google.com \
--cc=mhommey@mozilla.com \
--cc=tglek@mozilla.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).