Something that concerns me is a note from
https://gcc.gnu.org/gcc-6/changes.html :
"Value range propagation now assumes that the this pointer of C++ member
functions is non-null. This eliminates common null pointer checks but
also breaks some non-conforming code-bases (such as Qt-5, Chromium,
KDevelop). As a temporary work-around -fno-delete-null-pointer-checks
can be used. Wrong code can be identified by using -fsanitize=undefined."
Sounds like this has potential to break a significant number of packages.
On 04/18/2016 07:15 AM, Khem Raj wrote:
Hello all,
I have put together a potential gcc6 upgrade recipe set, and pushed the branch
to tree here
http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-6
and also at github fork of mine.
https://github.com/kraj/openembedded-core/tree/kraj/master
You need to set
GCCVERSION = “6.%”
in local.conf to enable it.
There are few recipes in OE-Core which still don’t compile e.g.
see
http://errors.yoctoproject.org/Errors/Build/14782/
any help in fixing them or otherwise fixing other layers is appreciated.
gcc6 is a major release for some info see
https://gcc.gnu.org/gcc-6/changes.html
and porting guide
https://gcc.gnu.org/gcc-6/porting_to.html
Thanks
-Khem
--
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel