From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
"openembedded-core@lists.openembedded.org oe-core layer"
<Openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] GCC 4.8 recipes
Date: Fri, 29 Mar 2013 15:55:14 +0100 [thread overview]
Message-ID: <20130329145514.GH11120@jama> (raw)
In-Reply-To: <6B577862-4C24-49DB-80F2-3A1408AF8337@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]
On Wed, Mar 27, 2013 at 10:51:50PM -0700, Khem Raj wrote:
> All,
>
> I have added gcc 4.8 recipes and the branch is here
>
> git://git.openembedded.org/openembedded-core-contrib kraj/gcc-4.8
>
> cgit
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-4.8
>
> Please test it out on your respective environments if you can.
First failed task in world rebuild:
| ar.c: In function 'do_oper_extract':
| ar.c:831:1: error: unrecognizable insn:
| }
| ^
| (insn 1893 1892 38 59 (parallel [
| (set (reg:SI 3 r3)
| (mem/c:SI (reg:SI 3 r3) [21 S4 A32]))
| (set (reg:SI 12 ip)
| (mem/c:SI (plus:SI (reg:SI 3 r3)
| (const_int 4 [0x4])) [21 S4 A32]))
| (set (reg/f:SI 13 sp)
| (mem/c:SI (plus:SI (reg:SI 3 r3)
| (const_int 8 [0x8])) [23 %sfp+-272 S4 A32]))
| ]) ar.c:639 -1
| (expr_list:REG_ARGS_SIZE (const_int 0 [0])
| (nil)))
| ar.c:831:1: internal compiler error: in extract_insn, at recog.c:2150
| arm-oe-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork --sysroot=/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/qemuarm -std=gnu99 -Wall -Wshadow -Werror -Wunused -Wextra -fgnu89-inline -Wformat=2 -O2 -pipe -g -feliminate-unused-debug-types -Wl,-rpath-link,../libelf:../libdw -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -o elfcmp elfcmp.o ../libebl/libebl.a ../libelf/libelf.so -ldl
| Please submit a full bug report,
| with preprocessed source if appropriate.
| See <http://gcc.gnu.org/bugs.html> for instructions.
| make[2]: *** [ar.o] Error 1
| make[2]: *** Waiting for unfinished jobs....
| rm i386_ld.o
| make[2]: Leaving directory `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/elfutils/0.148-r11/elfutils-0.148/src'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/elfutils/0.148-r11/elfutils-0.148'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/elfutils/0.148-r11/temp/log.do_compile.15119 for further information)
NOTE: recipe elfutils-0.148-r11: task do_compile: Failed
ERROR: Task 535 (/home/jenkins/oe/shr-core-branches/shr-core/openembedded-core/meta/recipes-devtools/elfutils/elfutils_0.148.bb, do_compile) failed with exit code '1'
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
"openembedded-core@lists.openembedded.org oe-core layer"
<Openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFT] GCC 4.8 recipes
Date: Fri, 29 Mar 2013 15:55:14 +0100 [thread overview]
Message-ID: <20130329145514.GH11120@jama> (raw)
In-Reply-To: <6B577862-4C24-49DB-80F2-3A1408AF8337@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]
On Wed, Mar 27, 2013 at 10:51:50PM -0700, Khem Raj wrote:
> All,
>
> I have added gcc 4.8 recipes and the branch is here
>
> git://git.openembedded.org/openembedded-core-contrib kraj/gcc-4.8
>
> cgit
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-4.8
>
> Please test it out on your respective environments if you can.
First failed task in world rebuild:
| ar.c: In function 'do_oper_extract':
| ar.c:831:1: error: unrecognizable insn:
| }
| ^
| (insn 1893 1892 38 59 (parallel [
| (set (reg:SI 3 r3)
| (mem/c:SI (reg:SI 3 r3) [21 S4 A32]))
| (set (reg:SI 12 ip)
| (mem/c:SI (plus:SI (reg:SI 3 r3)
| (const_int 4 [0x4])) [21 S4 A32]))
| (set (reg/f:SI 13 sp)
| (mem/c:SI (plus:SI (reg:SI 3 r3)
| (const_int 8 [0x8])) [23 %sfp+-272 S4 A32]))
| ]) ar.c:639 -1
| (expr_list:REG_ARGS_SIZE (const_int 0 [0])
| (nil)))
| ar.c:831:1: internal compiler error: in extract_insn, at recog.c:2150
| arm-oe-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork --sysroot=/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/sysroots/qemuarm -std=gnu99 -Wall -Wshadow -Werror -Wunused -Wextra -fgnu89-inline -Wformat=2 -O2 -pipe -g -feliminate-unused-debug-types -Wl,-rpath-link,../libelf:../libdw -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -o elfcmp elfcmp.o ../libebl/libebl.a ../libelf/libelf.so -ldl
| Please submit a full bug report,
| with preprocessed source if appropriate.
| See <http://gcc.gnu.org/bugs.html> for instructions.
| make[2]: *** [ar.o] Error 1
| make[2]: *** Waiting for unfinished jobs....
| rm i386_ld.o
| make[2]: Leaving directory `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/elfutils/0.148-r11/elfutils-0.148/src'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/elfutils/0.148-r11/elfutils-0.148'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/elfutils/0.148-r11/temp/log.do_compile.15119 for further information)
NOTE: recipe elfutils-0.148-r11: task do_compile: Failed
ERROR: Task 535 (/home/jenkins/oe/shr-core-branches/shr-core/openembedded-core/meta/recipes-devtools/elfutils/elfutils_0.148.bb, do_compile) failed with exit code '1'
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-03-29 15:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 5:51 [RFT] GCC 4.8 recipes Khem Raj
2013-03-28 7:36 ` Yi Qingliang
2013-03-28 8:29 ` Koen Kooi
2013-03-28 9:49 ` Yi Qingliang
2013-03-28 9:02 ` Marcin Juszkiewicz
2013-03-28 15:46 ` Marcin Juszkiewicz
2013-03-28 16:07 ` Khem Raj
2013-03-28 17:49 ` Richard Purdie
2013-03-29 8:13 ` Elvis Dowson
2013-03-29 8:13 ` [OE-core] " Elvis Dowson
2013-03-29 8:18 ` Khem Raj
2013-03-29 8:18 ` [OE-core] " Khem Raj
2013-03-29 14:55 ` Martin Jansa [this message]
2013-03-29 14:55 ` Martin Jansa
2013-03-30 9:03 ` Martin Jansa
2013-03-30 9:03 ` [OE-core] " Martin Jansa
2013-04-01 9:52 ` Martin Jansa
2013-04-01 9:52 ` [OE-core] " Martin Jansa
2013-04-02 14:22 ` Khem Raj
2013-04-02 14:22 ` [OE-core] " Khem Raj
2013-04-20 0:32 ` Khem Raj
2013-04-20 0:32 ` [OE-core] " Khem Raj
2013-05-10 12:53 ` Martin Jansa
2013-05-10 12:53 ` [OE-core] " Martin Jansa
2013-05-14 16:29 ` [RFC][PATCH] gcc-4.8: temporary disable thumb Martin Jansa
2013-05-14 21:14 ` Khem Raj
2013-09-18 23:58 ` [PATCH] " Martin Jansa
2013-04-11 14:23 ` [RFT] GCC 4.8 recipes Jack Mitchell
2013-04-15 2:14 ` Khem Raj
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=20130329145514.GH11120@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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 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.