public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: hbusch@bnv-bamberg.de
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: g++ version 7.5.0 and library <memory_resource>
Date: Mon, 08 Jun 2020 13:44:12 +0200	[thread overview]
Message-ID: <20200608134412.Horde.mIJ7NQthkPEbn-W1QLIxrj9@webmail.bnv-bamberg.de> (raw)
In-Reply-To: <CAH6eHdQMpPP_N_N3tYSzTDRwMs-0nJDJa2S+JcCzFS+wg9jgTg@mail.gmail.com>

You are right Jonathan, at least I do not get an error from the  
compiler complaining about <memory_resource> when I use  
<experimental/memory_resource>.

However, the next hurdle for the compiler is the following statement:

std::pmr::monotonic_buffer_resource ...

So at least this seems not be be included.

Thanks for your kind help here.

Best regards
Harald


Thanks a lot Jonatahan f

Quoting Jonathan Wakely <jwakely.gcc@gmail.com>:

> On Mon, 8 Jun 2020 at 05:43, <hbusch@bnv-bamberg.de> wrote:
>>
>> Thanks a lot Marc for your quick help.
>> Even <experimental/memory_resource> did not help.
>>
>> Here ...
>>
>> https://gcc.gnu.org/onlinedocs/gcc-7.5.0/libstdc++/manual/manual/status.html#status.iso.2017
>>
>> ... I see that 7.5.0 does not include memory_resource.
>
> But <experimental/memory_resource> and <memory_resource> are two
> different headers.
>
> GCC 7.5.0 *does* provide <experimental/memory_resource>, as documented
> in Table 1.4 at
> https://gcc.gnu.org/onlinedocs/gcc-7.5.0/libstdc++/manual/manual/status.html#status.iso.2014
> where it shows that the "Polymorphic memory resources" component of
> the Library Fundamental Techncial Specification is partially
> supported.







  reply	other threads:[~2020-06-08 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 19:10 hbusch
2020-06-07 19:18 ` Marc Glisse
2020-06-08  4:42   ` hbusch
2020-06-08  7:46     ` Jonathan Wakely
2020-06-08 11:44       ` hbusch [this message]
2020-06-08 14:34         ` Jonathan Wakely
2020-06-07 21:56 ` Jonathan Wakely
2020-06-08  4:40   ` hbusch

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=20200608134412.Horde.mIJ7NQthkPEbn-W1QLIxrj9@webmail.bnv-bamberg.de \
    --to=hbusch@bnv-bamberg.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).