From: Martin Jansa <martin.jansa@gmail.com>
To: Dan McGregor <danismostlikely@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: [RFT] GCC 8.1
Date: Mon, 14 May 2018 19:09:41 +0200 [thread overview]
Message-ID: <20180514170941.GC2840@jama> (raw)
In-Reply-To: <CACS+7ZRs_zB_c-Wg8K=JEtWyHH7DG-W8ER4Ky1Yg6v1C8xtsyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3168 bytes --]
On Mon, May 14, 2018 at 10:33:41AM -0600, Dan McGregor wrote:
> On 10 May 2018 at 12:53, Khem Raj <raj.khem@gmail.com> wrote:
> > Hi Dan,
> >
> > Thanks for testing
> >
> > On 5/10/18 7:34 AM, Dan McGregor wrote:
> >>
> >> On 4 May 2018 at 18:26, Khem Raj <raj.khem@gmail.com> wrote:
> >>>
> >>> Hi All
> >>>
> >>> As you might have noticed that gcc 8.1 was released this week, I am
> >>> calling out for some testing help on testing branch so we can weed out
> >>> issues you might see in your setups. so if you have your
> >>> builders idling over weekend, then you know what they can do this weekend
> >>> :)
> >>>
> >>
> >> Thanks for this. The only two issues I noticed are that the
> >> Wandboard's kernel doesn't compile with gcc 8.1,
> >
> >
> >
> > what errors do you see ?
>
> I expect the standard "Linux 4.1" errors. A bunch of ignored
> attributes and incompatible type aliases:
>
> tmp-glibc/work-shared/wandboard/kernel-source/include/linux/log2.h:22:1:
> warning: ignoring attribute 'noreturn' because it conflicts with
> attribute 'const' [-Wattributes]
> int ____ilog2_NaN(void)
Try backporting this change:
https://github.com/torvalds/linux/commit/474c90156c8dcc2fa815e6716cc9394d7930cb9c
> tmp-glibc/work-shared/wandboard/kernel-source/include/linux/syscalls.h:195:18:
> warning: 'sys_clone' alias between functions of incompatible types
> 'long int(long unsigned int, long unsigned int, int *, int, int *)'
> and 'long int(long int, long int, long int, long int, long int)'
> [-Wattribute-alias]
> asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
>
> I can give you the full compile log if you'd like, but I think others
> want it kept off the list.
>
> >
> > and gcc-sanitizers
> >>
> >> now throws a packaging error on (at least) x86_64.
> >> ${libdir}/liblsan_preinit.o is a new file that should go into
> >> liblsan-dev.
> >
> >
> > That seems to be the case, I wonder why my world build for qemux86_64 did
> > not find this error. I would like to reproduce this and the fix is then
> > simple.
>
> My x86_64 build was multilib enabled. I doubt that had anything to do
> with it, but I suppose it's possible.
>
> >
> >
> >>
> >>> Highlighted changes are
> >>>
> >>> https://gcc.gnu.org/gcc-8/changes.html
> >>>
> >>> and porting doc is
> >>>
> >>> https://gcc.gnu.org/gcc-8/porting_to.html
> >>>
> >>> The branch is here
> >>>
> >>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-8
> >>>
> >>> Its uptodate on top of current master oe-core
> >>>
> >>> May fourth be with you !!
> >>>
> >>> Cheers!
> >>>
> >>> -Khem
> >>> --
> >>> _______________________________________________
> >>> Openembedded-core mailing list
> >>> Openembedded-core@lists.openembedded.org
> >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2018-05-14 17:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:26 [RFT] GCC 8.1 Khem Raj
2018-05-09 9:38 ` Martin Jansa
2018-05-10 12:20 ` [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc Martin Jansa
2018-05-10 13:01 ` Burton, Ross
2018-05-10 18:21 ` Khem Raj
2018-05-10 18:24 ` Khem Raj
2018-05-10 19:16 ` Martin Jansa
2018-05-10 19:26 ` Khem Raj
2018-05-30 17:39 ` Andre McCurdy
2018-06-10 11:05 ` Martin Jansa
2018-05-10 18:50 ` [RFT] GCC 8.1 Khem Raj
2018-05-10 19:11 ` Martin Jansa
2018-05-10 19:27 ` Andre McCurdy
2018-05-10 21:43 ` Martin Jansa
2018-05-10 22:07 ` Martin Jansa
2018-05-10 22:35 ` Khem Raj
2018-05-10 22:38 ` Andre McCurdy
2018-05-10 22:38 ` Martin Jansa
2018-05-10 22:40 ` Andre McCurdy
2018-05-10 22:50 ` Martin Jansa
2018-05-10 23:11 ` Andre McCurdy
2018-05-10 23:32 ` Martin Jansa
2018-05-10 23:41 ` Andre McCurdy
2018-05-11 0:55 ` Khem Raj
2018-05-11 1:00 ` Andre McCurdy
2018-05-11 1:06 ` Khem Raj
2018-05-11 1:11 ` Andre McCurdy
2018-05-11 1:16 ` Khem Raj
2018-05-11 1:21 ` Andre McCurdy
2018-05-17 10:46 ` Martin Jansa
2018-05-18 5:54 ` Khem Raj
2018-05-24 15:08 ` Martin Jansa
2018-05-10 14:34 ` Dan McGregor
2018-05-10 18:53 ` Khem Raj
2018-05-14 16:33 ` Dan McGregor
2018-05-14 17:09 ` Martin Jansa [this message]
[not found] ` <CAGAf8LxceSXvK-pgfWYDvYLmcvMMK0D5q==PKG9jeRWs6YEbGA@mail.gmail.com>
2018-05-10 19:21 ` [yocto] " Khem Raj
2018-05-11 22:05 ` Burton, Ross
2018-05-12 6:10 ` Khem Raj
2018-05-13 23:35 ` 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=20180514170941.GC2840@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=danismostlikely@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox