From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: GCC 4.3 fails to build glibc(-intermediate)
Date: Wed, 28 May 2008 09:36:39 +0200 [thread overview]
Message-ID: <g1j228$7m8$1@ger.gmane.org> (raw)
In-Reply-To: <1211958108.27777.15.camel@isis>
Khem Raj wrote:
> On Thu, 2008-05-22 at 16:11 +0200, Enric Balletbò i Serra wrote:
>> Hi,
>>
>> I have the same problem, but at this moment I don't have idea about solution.
>
> I could reproduce this problem as well. I also tried to reduce the
> issue. It is an ICE in GCC and I have made a small testcase which I am
> able to reproduce on gcc-4_3-branch I have reported a gcc bug(PR36350)
> for it Meanwhile you can remove -frename-registers optimization pass
> and ICE should go away.
And now I know why I wasn't seeing the ICE when using gcc 4.3.0: I
turned off -frename-registers and -ftree-vectorize for armv7a
completely, since gcc threw an ICE....
regards,
Koen
>
> Something like this might work around for glibc
>
> Index: libc/iconv/Makefile
> ===================================================================
> --- libc.orig/iconv/Makefile 2008-05-27 23:50:05.000000000 -0700
> +++ libc/iconv/Makefile 2008-05-27 23:54:43.000000000 -0700
> @@ -38,6 +38,8 @@
> CFLAGS-gconv_simple.c = -DSTATIC_GCONV
> endif
>
> +CFLAGS-gconv_simple.c += -fno-rename-registers
> +
> vpath %.c ../locale/programs ../intl
>
> iconv_prog-modules = iconv_charmap charmap charmap-dir linereader \
>
>
> Thanks
>
> -Khem
>
>> Regards,
>> Enric Balletbo i Serra
>>
>> On Wed, May 7, 2008 at 7:33 AM, Matthijs van de Water
>> matthijs.van.de.water at gmail.com wrote:
>>
>>> Hi,
>>>
>>> I'm trying to get an ARM EABI build based on gcc 4.3 working. I'm not
>>> having much luck with that so-far.
>>>
>>> The build fails at glibc-internal (tried both 2.6.1 and 2.7) with an
>>> internal compiler error:
>>> ../iconv/skeleton.c: In function '__gconv_transform_ucs4_internal':
>>> ../iconv/skeleton.c:801: internal compiler error: Segmentation fault
>>>
>>> Am I missing something? Any ideas?
>>>
>>> Regards,
>>>
>>> Matthijs van de Water
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel at lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-05-28 7:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70c9a9110805220710x6663f582lc5d6b75744960d08@mail.gmail.com>
2008-05-22 14:11 ` GCC 4.3 fails to build glibc(-intermediate) Enric Balletbò i Serra
2008-05-22 15:44 ` Khem Raj
2008-05-22 18:24 ` Rolf Leggewie
2008-05-23 0:02 ` Khem Raj
2008-05-23 6:17 ` Rolf Leggewie
2008-05-23 6:36 ` Rolf Leggewie
2008-05-28 7:01 ` Khem Raj
2008-05-28 7:36 ` Koen Kooi [this message]
2008-05-28 9:52 ` Matthijs van de Water
2008-05-28 11:22 ` Rolf Leggewie
2008-06-03 7:16 ` Matthijs van de Water
2008-06-04 11:14 ` Koen Kooi
2008-06-04 23:22 ` Khem Raj
2008-05-07 14:33 Matthijs van de Water
2008-05-07 16:21 ` Khem Raj
2008-05-07 17:02 ` Matthijs van de Water
2008-05-07 18:31 ` Leon Woestenberg
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='g1j228$7m8$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.