All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Ambrożewicz" <adrian.ambrozewicz@linux.intel.com>
To: Andrew Geissler <geissonator@gmail.com>,
	Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Upstream Yocto Bringing in GCC 10
Date: Mon, 25 May 2020 14:35:32 +0200	[thread overview]
Message-ID: <7f027233-e0c5-552d-82da-cd3a30d74009@linux.intel.com> (raw)
In-Reply-To: <2E02F120-7D24-48BE-AFD8-9A7ADD0F08E5@gmail.com>



W dniu 5/22/2020 o 02:36, Andrew Geissler pisze:
> 
> 
>> On May 17, 2020, at 7:08 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
>>
>> On Sun, May 17, 2020 at 12:19:39PM -0500, Andrew Geissler wrote:
>>> Ready or not, this weeks upstream update brought in GCC 10 (along with the normal slew of new packages).
>>
>> Alright!  The great thing about GCC 10.x is that it brings in support
>> for most of C++20, including co-routines.  Looking forward to playing
>> around with it.
Is it allowed in OpenBMC to base the functionality on experimental 
implementations?

> 
> It took a few more patches but GCC 10 is now in openbmc master.
> Our unit test CI framework has also been updated to run with GCC 10.
> 
> We also migrated from clang-8 to clang-10 in CI so you may want
> to take a look at a recommended clang format update in this commit:
> https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/32696
> 
> You may see some new CI fails with your existing code. It could be
> the clang format noted above or some code that is not exercised
> as a part of our normal machine builds. If you hit an issue, it’s
> probably been fixed somewhere in our code base already so
> browse over this commit list for your issue:
> https://gerrit.openbmc-project.xyz/q/topic:%22upstream%22+(status:open%20OR%20status:merged)
> 
> There were a lot of include related issues where you just need
> to include the needed header files.
> 
> Andrew
> 
>>
>> -- 
>> Patrick Williams
> 
Great progress :)

Regards,
Adrian

  reply	other threads:[~2020-05-25 12:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 17:19 Upstream Yocto Bringing in GCC 10 Andrew Geissler
2020-05-18  0:08 ` Patrick Williams
2020-05-22  0:36   ` Andrew Geissler
2020-05-25 12:35     ` Adrian Ambrożewicz [this message]
2020-05-26 12:33       ` Brad Bishop
2020-05-26 15:57       ` Patrick Williams
2020-06-02  8:18         ` Adrian Ambrożewicz
2020-06-02 18:32           ` Khetan, Sharad
2020-06-02 20:09             ` Patrick Williams
2020-06-02 22:12               ` Richard Hanley
2020-06-02 22:55                 ` Patrick Williams
2020-06-02 23:02                   ` William Kennington

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=7f027233-e0c5-552d-82da-cd3a30d74009@linux.intel.com \
    --to=adrian.ambrozewicz@linux.intel.com \
    --cc=geissonator@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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.