Skip to contentSkip to conversation

tcmode-default: Set 4.8 as default

RFC In review Saul Wold 8 participants 15 messages May 12, 2013 – Jun 12, 2013

lore
Share & tools
lore

Saul Wold

author
#0 lore raw

RFC 1/1 tcmode-default: Set 4.8 as default

This changes the default GCC to 4.8, it has been tested with OE-Core and a number of layers have been testing with it for the last few weeks.

There are some minor issues outside of OE-Core. These will be addressed with time.

---
 meta/conf/distro/include/tcmode-default.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/distro/include/tcmode-default.inc +1 -1
index 88d109b..f3942b5 100644
@@ -17,7 +17,7 @@ PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = "${TCLIBC}-initial"
 PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial = "nativesdk-${TCLIBC}-initial"
 PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
 
-GCCVERSION ?= "4.7%"
+GCCVERSION ?= "4.8%"
 SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.23.2"
 EGLIBCVERSION ?= "2.17"
Signature · 1 line
1.8.0.2
#1 lore raw

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted is it working for you ?

-Khem

Quoted 29 lines · Saul Wold

This changes the default GCC to 4.8, it has been tested with OE-Core and a number of layers have been testing with it for the last few weeks.

There are some minor issues outside of OE-Core. These will be addressed with time.

---
meta/conf/distro/include/tcmode-default.inc | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/distro/include/tcmode-default.inc +0 -0
index 88d109b..f3942b5 100644
@@ -17,7 +17,7 @@ PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = "${TCLIBC}-initial"

PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial = "nativesdk-${TCLIBC}-initial" PREFERRED_PROVIDER_virtual/gettext ??= "gettext"

meta/conf/distro/include/tcmode-default.inc +1 -1
-GCCVERSION ?= "4.7%"
+GCCVERSION ?= "4.8%"

SDKGCCVERSION ?= "${GCCVERSION}"
BINUVERSION ?= "2.23.2"
EGLIBCVERSION ?= "2.17"

Signature · 1 line
1.8.0.2
author
#2 lore raw
Quoted 5 lines · Khem Raj

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted is it working for you ?

Nope your right there does appear to be a problem with ARM, I thought we where have sanity test issues again, I just completed a build and verified that I get a Kernel paninc with 3.8 Kernel and 4.8 GCC.

Not ready yet!

Khem, are you looking into it? I have CC'ed Bruce for the kernel also.

Sau!

Quoted 34 lines

-Khem

Quoted 29 lines · Saul Wold

This changes the default GCC to 4.8, it has been tested with OE-Core and a number of layers have been testing with it for the last few weeks.

There are some minor issues outside of OE-Core. These will be addressed with time.

---
meta/conf/distro/include/tcmode-default.inc | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/distro/include/tcmode-default.inc +0 -0
index 88d109b..f3942b5 100644
@@ -17,7 +17,7 @@ PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = "${TCLIBC}-initial"

PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial = "nativesdk-${TCLIBC}-initial" PREFERRED_PROVIDER_virtual/gettext ??= "gettext"

meta/conf/distro/include/tcmode-default.inc +1 -1
-GCCVERSION ?= "4.7%"
+GCCVERSION ?= "4.8%"

SDKGCCVERSION ?= "${GCCVERSION}"
BINUVERSION ?= "2.23.2"
EGLIBCVERSION ?= "2.17"
--
1.8.0.2

#3 lore raw
Quoted 11 lines · Saul Wold
Quoted 5 lines · Khem Raj

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted is it working for you ?

Nope your right there does appear to be a problem with ARM, I thought we where have sanity test issues again, I just completed a build and verified that I get a Kernel paninc with 3.8 Kernel and 4.8 GCC.

Not ready yet!

Khem, are you looking into it? I have CC'ed Bruce for the kernel also.

haven't looked into the problem in detail. Its one of those either a problem in gcc or gcc uncovering a latent bug in kernel.

#4 lore raw
Quoted 9 lines · Khem Raj
Quoted 6 lines · Saul Wold
Quoted 5 lines · Khem Raj

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted is it working for you ?

Quoted 7 lines
Quoted 5 lines

Nope your right there does appear to be a problem with ARM, I thought we where have sanity test issues again, I just completed a build and verified that I get a Kernel paninc with 3.8 Kernel and 4.8 GCC.

Not ready yet!

Khem, are you looking into it? I have CC'ed Bruce for the kernel also.

haven't looked into the problem in detail. Its one of those either a problem in gcc or gcc uncovering a latent bug in kernel.

I'll get myself set up and do a build on Monday, see if anything obvious pops up (i.e. start with the latest and see if it works, then bisect back). I'm already poking at mips64, so I can do this in parallel.

Bruce

Quoted 2 lines
#5 lore raw
Quoted 16 lines · Bruce Ashfield
Quoted 15 lines · Khem Raj
Quoted 11 lines · Saul Wold
Quoted 5 lines · Khem Raj

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted is it working for you ?

Nope your right there does appear to be a problem with ARM, I thought we where have sanity test issues again, I just completed a build and verified that I get a Kernel paninc with 3.8 Kernel and 4.8 GCC.

Not ready yet!

Khem, are you looking into it? I have CC'ed Bruce for the kernel also.

Quoted 11 lines
Quoted 1 line

haven't looked into the problem in detail. Its one of those either a problem in gcc or gcc uncovering a latent bug in kernel.

I'll get myself set up and do a build on Monday, see if anything obvious pops up (i.e. start with the latest and see if it works, then bisect back). I'm already poking at mips64, so I can do this in parallel.

Bruce

Quoted 2 lines

I know the beaglebone kernel was segfaulting on me until Koen updated to 3.8.11, I think it included some important backports. Would definitely be worth a try, Koen can point to you to commit which fixed it, I seem to have lost the link into the IRC nether.

Cheers,

Signature · 5 lines
  Jack Mitchell ([email protected])
  Embedded Systems Engineer
  http://www.embed.me.uk

--
#6 lore raw

Op 13 mei 2013, om 10:41 heeft Jack Mitchell <[email protected]> het volgende geschreven:

Quoted 23 lines · Bruce Ashfield
Quoted 22 lines · Khem Raj
Quoted 9 lines · Saul Wold
Quoted 7 lines · Khem Raj
Quoted 5 lines

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted is it working for you ?

Quoted 7 lines
Quoted 5 lines

Nope your right there does appear to be a problem with ARM, I thought we where have sanity test issues again, I just completed a build and verified that I get a Kernel paninc with 3.8 Kernel and 4.8 GCC.

Not ready yet!

Khem, are you looking into it? I have CC'ed Bruce for the kernel also.

haven't looked into the problem in detail. Its one of those either a problem in gcc or gcc uncovering a latent bug in kernel.

I'll get myself set up and do a build on Monday, see if anything obvious pops up (i.e. start with the latest and see if it works, then bisect back). I'm already poking at mips64, so I can do this in parallel.

Quoted 7 lines
Quoted 5 lines

Bruce

Quoted 2 lines

I know the beaglebone kernel was segfaulting on me until Koen updated to 3.8.11, I think it included some important backports. Would definitely be worth a try, Koen can point to you to commit which fixed it, I seem to have lost the link into the IRC nether.

I'm fairly sure this is the one:

	http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=84237e8d1b43b896a86e14928993901993ede254

I only tested the 3.8.10 -> 3.811 update in one go, so it could a different patch.

regars,

Koen

#7 lore raw
In reply to Jack Mitchell
Quoted 38 lines · Jack Mitchell
Quoted 27 lines · Bruce Ashfield
Quoted 16 lines · Khem Raj
Quoted 12 lines · Saul Wold
Quoted 7 lines · Khem Raj

Hi Saul

There is one serious problem that I ran into was that qemuarm 3.8 kernel segfaulted
is it working for you ?

Nope your right there does appear to be a problem with ARM, I thought we where have sanity test issues again, I just completed a build and verified that I get a Kernel paninc with 3.8 Kernel and 4.8 GCC.

Quoted 7 lines
Quoted 3 lines

Not ready yet!

Khem, are you looking into it? I have CC'ed Bruce for the kernel also.

haven't looked into the problem in detail. Its one of those either a problem in gcc or gcc uncovering a latent bug in kernel.

Quoted 9 lines

I'll get myself set up and do a build on Monday, see if anything obvious pops up (i.e. start with the latest and see if it works, then bisect back). I'm already poking at mips64, so I can do this in parallel.

Bruce

Quoted 2 lines
Quoted 4 lines

I know the beaglebone kernel was segfaulting on me until Koen updated to 3.8.11, I think it included some important backports. Would definitely be worth a try, Koen can point to you to commit which fixed it, I seem to have lost the link into the IRC nether.

Luckily I have the latest 3.8.x ready to go, and we are already on 3.8.11, so as Koen indicated in his follow up, it may be a patch in 3.8.11 + something else. I'll start with my latest 3.8 tree, and then use 3.9 and 3.10 respectively until I can find the patch.

That being said, if anyone else bisects and finds the fix, I'll be happy to merge
a change, or take the confirmation that it's in the pending -stable update.

Bruce

Quoted 9 lines

Cheers,

--

Jack Mitchell ([email protected])
Embedded Systems Engineer
http://www.embed.me.uk

Quoted 8 lines

--

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

#8 lore raw
In reply to Saul Wold
Quoted 18 lines · Saul Wold

This changes the default GCC to 4.8, it has been tested with OE-Core and a number of layers have been testing with it for the last few weeks.

There are some minor issues outside of OE-Core. These will be addressed with time.

---
 meta/conf/distro/include/tcmode-default.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/conf/distro/include/tcmode-default.inc +0 -0
index 88d109b..f3942b5 100644

meta/conf/distro/include/tcmode-default.inc PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = "${TCLIBC}-initial" · line 23

Quoted 8 lines
meta/conf/distro/include/tcmode-default.inc +1 -1
@@ -17,7 +17,7 @@ PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = "${TCLIBC}-initial"
 PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial = "nativesdk-${TCLIBC}-initial"
 PREFERRED_PROVIDER_virtual/gettext ??= "gettext"
 
-GCCVERSION ?= "4.7%"
+GCCVERSION ?= "4.8%"
 SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.23.2"
 EGLIBCVERSION ?= "2.17"

There is also ICE when pixman is built with thumb enabled (e.g. qemuarm
+ ARM_INSTRUCTION_SET = "thumb" set, with thumb disabled it builds fine.

OE @ ~/oe-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/pixman/1_0.29.4-r0/pixman-0.29.4/test $ make
../arm-oe-linux-gnueabi-libtool --tag=CC --mode=compile arm-oe-linux-gnueabi-gcc -march=armv5te -mthumb -mthumb-interwork --sysroot=/OE/oe-core/tmp-eglibc/sysroots/qemuarm -DHAVE_CONFIG_H -I. -I.. -I../pixman -I../pixman -I/OE/oe-core/tmp-eglibc/sysroots/qemuarm/usr/include/libpng16 -O2 -pipe -g -feliminate-unused-debug-types -Wall -fno-strict-aliasing -fvisibility=hidden -c -o utils-prng.lo utils-prng.c
arm-oe-linux-gnueabi-libtool: compile: arm-oe-linux-gnueabi-gcc -march=armv5te -mthumb -mthumb-interwork --sysroot=/OE/oe-core/tmp-eglibc/sysroots/qemuarm -DHAVE_CONFIG_H -I. -I.. -I../pixman -I../pixman -I/OE/oe-core/tmp-eglibc/sysroots/qemuarm/usr/include/libpng16 -O2 -pipe -g -feliminate-unused-debug-types -Wall -fno-strict-aliasing -fvisibility=hidden -c utils-prng.c -fPIC -DPIC -o .libs/utils-prng.o utils-prng.c: In function 'prng_srand_r':
utils-prng.c:73:1: internal compiler error: Segmentation fault
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [utils-prng.lo] Error 1

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#9 lore raw

PATCH 1/1 pixman: temporary disable thumb

* building with thumb triggers ICE with gcc-4.8
OE @ ~/oe-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/pixman/1_0.29.4-r0/pixman-0.29.4/test $ make
../arm-oe-linux-gnueabi-libtool --tag=CC --mode=compile arm-oe-linux-gnueabi-gcc -march=armv5te -mthumb -mthumb-interwork
--sysroot=/OE/oe-core/tmp-eglibc/sysroots/qemuarm -DHAVE_CONFIG_H -I. -I.. -I../pixman -I../pixman
-I/OE/oe-core/tmp-eglibc/sysroots/qemuarm/usr/include/libpng16 -O2 -pipe -g -feliminate-unused-debug-types -Wall -fno-strict-aliasing -fvisibility=hidden
-c -o utils-prng.lo utils-prng.c
arm-oe-linux-gnueabi-libtool: compile: arm-oe-linux-gnueabi-gcc -march=armv5te -mthumb -mthumb-interwork --sysroot=/OE/oe-core/tmp-eglibc/sysroots/qemuarm -DHAVE_CONFIG_H -I. -I.. -I../pixman -I../pixman -I/OE/oe-core/tmp-eglibc/sysroots/qemuarm/usr/include/libpng16 -O2 -pipe -g -feliminate-unused-debug-types -Wall -fno-strict-aliasing -fvisibility=hidden -c utils-prng.c -fPIC -DPIC -o .libs/utils-prng.o
utils-prng.c: In function 'prng_srand_r':
utils-prng.c:73:1: internal compiler error: Segmentation fault
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [utils-prng.lo] Error 1

---
 meta/recipes-graphics/xorg-lib/pixman_0.29.4.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-graphics/xorg-lib/pixman_0.29.4.bb +2 -0
index b1bd557..7cc5a74 100644
@@ -23,6 +23,8 @@ NEON = " --disable-arm-neon "
 NEON_armv7a = " "
 NEON_armv7a-vfp-neon = " "
 
+ARM_INSTRUCTION_SET = "arm"
+
 EXTRA_OECONF = "--disable-gtk ${IWMMXT} ${LOONGSON_MMI} ${NEON}"
 EXTRA_OECONF_class-native = "--disable-gtk"
 
Signature · 1 line
1.8.2.1
#10 lore raw

PATCH v2 1/1 pixman: temporary disable thumb

* building with thumb triggers ICE with gcc-4.8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57329

---
 meta/recipes-graphics/xorg-lib/pixman_0.29.4.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-graphics/xorg-lib/pixman_0.29.4.bb +2 -0
index b1bd557..7cc5a74 100644
@@ -23,6 +23,8 @@ NEON = " --disable-arm-neon "
 NEON_armv7a = " "
 NEON_armv7a-vfp-neon = " "
 
+ARM_INSTRUCTION_SET = "arm"
+
 EXTRA_OECONF = "--disable-gtk ${IWMMXT} ${LOONGSON_MMI} ${NEON}"
 EXTRA_OECONF_class-native = "--disable-gtk"
 
Signature · 1 line
1.8.2.1
#11 lore raw

Re: [PATCHv2] pixman: temporary disable thumb

Quoted 2 lines · Martin Jansa

* building with thumb triggers ICE with gcc-4.8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57329

This patch is superseded by
http://patchwork.openembedded.org/patch/51567/
which fixes this issue.

Quoted 22 lines
---
 meta/recipes-graphics/xorg-lib/pixman_0.29.4.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-graphics/xorg-lib/pixman_0.29.4.bb +2 -0
index b1bd557..7cc5a74 100644
@@ -23,6 +23,8 @@ NEON = " --disable-arm-neon "
 NEON_armv7a = " "
 NEON_armv7a-vfp-neon = " "
 
+ARM_INSTRUCTION_SET = "arm"
+
 EXTRA_OECONF = "--disable-gtk ${IWMMXT} ${LOONGSON_MMI} ${NEON}"
 EXTRA_OECONF_class-native = "--disable-gtk"
 
Signature · 1 line
1.8.2.1
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#13 lore raw
Quoted 7 lines · Phil Blundell
Quoted 3 lines · Martin Jansa

Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Did you do that? Please add the PR number to the check message so we can tell when it's been fixed.

Not yet, I'm trying to strip test case from pixman, but sofar I can reproduce it only with significant chunk of pixman code.

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#14 lore raw
Quoted 11 lines · Martin Jansa
Quoted 7 lines · Phil Blundell
Quoted 3 lines · Martin Jansa

Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Did you do that? Please add the PR number to the check message so we can tell when it's been fixed.

Not yet, I'm trying to strip test case from pixman, but sofar I can reproduce it only with significant chunk of pixman code.

That doesn't matter. Unless the testcase is hundreds of megabytes, you don't need to make heroic efforts to reduce it. Just go ahead and file a bug using whatever file you found the problem in.

p.