Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Naveen Saini" <naveen.kumar.saini@intel.com>
To: Khem Raj <raj.khem@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>,
	Randy MacLeod <randy.macleod@windriver.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFT][PATCH 0/2] GCC 11 Pre-release
Date: Mon, 12 Apr 2021 07:08:11 +0000	[thread overview]
Message-ID: <2e67319e33b141cf9b772dafd87217de@intel.com> (raw)
In-Reply-To: <CAMKF1spGGNJJ2bKVxjwikTDepYhsbeb0tqScQ2wU5UVGS_3LdA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]

(SWAT) Listing remaining failures:

qemu launch failure testimage:
https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/3278/steps/14/logs/stdio

LTP failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1798/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/1648/steps/12/logs/stdio


From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of Khem Raj
Sent: Sunday, April 11, 2021 1:58 AM
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>; Randy MacLeod <randy.macleod@windriver.com>; openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFT][PATCH 0/2] GCC 11 Pre-release

Thanks for testing it out I think I will try to address them in a follow up perhaps next week

On Sat, Apr 10, 2021 at 8:13 AM Richard Purdie <richard.purdie@linuxfoundation.org<mailto:richard.purdie@linuxfoundation.org>> wrote:
On Tue, 2021-03-30 at 14:30 -0700, Khem Raj wrote:
> This patchset updates to upcoming gcc 11 release, Please give it a try
> in your test beds if you have cycles, since there is still sometime left
> for final GCC 11 release perhaps we can squeeze in some bugfixes
>
> They are also available via git here
> https://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-11

I ran this through with the gnutls fix you found. There appear to be
reproducubility issues in gcc:

https://autobuilder.yoctoproject.org/typhoon/#/builders/118/builds/159/steps/12/logs/stdio

An issue with meta-mingw:

https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/3296

Missing maintainers entry:

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2004

valgrind ptest regressions on x86 and arm (even with the valgrind upgrade):

https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1688/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/1976/steps/12/logs/stdio

Cheers,

Richard

[-- Attachment #2: Type: text/html, Size: 6311 bytes --]

  reply	other threads:[~2021-04-12  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 21:30 [RFT][PATCH 0/2] GCC 11 Pre-release Khem Raj
2021-03-30 21:30 ` [PATCH 1/2] gcc: Upgrade to GCC 11 Khem Raj
2021-03-30 21:30 ` [PATCH 2/2] libgcc-initial: Do not build fp128 to decimal ppc functions Khem Raj
2021-04-10 15:13 ` [OE-core] [RFT][PATCH 0/2] GCC 11 Pre-release Richard Purdie
2021-04-10 17:58   ` Khem Raj
2021-04-12  7:08     ` Naveen Saini [this message]
2021-04-12  9:45       ` Richard Purdie

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=2e67319e33b141cf9b772dafd87217de@intel.com \
    --to=naveen.kumar.saini@intel.com \
    --cc=JPEWhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.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