All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: "Adrian Ambrożewicz" <adrian.ambrozewicz@linux.intel.com>
Cc: Andrew Geissler <geissonator@gmail.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Upstream Yocto Bringing in GCC 10
Date: Tue, 26 May 2020 10:57:56 -0500	[thread overview]
Message-ID: <20200526155756.GC3445@heinlein> (raw)
In-Reply-To: <7f027233-e0c5-552d-82da-cd3a30d74009@linux.intel.com>

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

On Mon, May 25, 2020 at 02:35:32PM +0200, Adrian Ambrożewicz wrote:
>> On May 17, 2020, at 7:08 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
>> 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?

No disagreement with how Brad responded to this.  In the past we've been
pretty prompt at moving up to the new C++ standards.

I am curious what you meant by "experimental implementations" here
though.  Usually the C++ standards committee has put things in the
'std::experimental' namespace when they are so and the normal 'std' is
non-experimental.  This means code using 'std' APIs should continue to
work going forward, but code using 'std::experimental' might not.

The specific example I mentioned here of coroutines is out of
std::experimental as of C++20.  The compiler writers have been slow to
get it implemented because it is a complicated feature.  So, I guess
you could consider the fresh implementation at the compiler level as
"experimental" but the language / library features themselves are not?

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-05-26 15:58 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
2020-05-26 12:33       ` Brad Bishop
2020-05-26 15:57       ` Patrick Williams [this message]
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=20200526155756.GC3445@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=adrian.ambrozewicz@linux.intel.com \
    --cc=geissonator@gmail.com \
    --cc=openbmc@lists.ozlabs.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 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.