From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
Date: Sun, 12 Feb 2023 11:20:21 +0000 [thread overview]
Message-ID: <9060022e-5e3b-e85f-b9e4-9b7beb265550@jguk.org> (raw)
In-Reply-To: <CAH6eHdS8RLSPZmmu6Q5wmjuhRiO2j2dt0JJp8hFjdG6d4NTJmg@mail.gmail.com>
On 12/02/2023 01:33, Jonathan Wakely wrote:
>
>
> On Sat, 11 Feb 2023, 23:38 Jonny Grant, <jg@jguk.org <mailto:jg@jguk.org>> wrote:
>
> Hello
>
> Anyone else seeing an issue when using c++23 ?
> gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
>
> The only change is to use --std=c++23
>
>
> With C++17 std::string is instantiated in the library, not in your code. With C++20 your code instantiates it. That's the only reason the -std option matters here.
Ok I see.
next prev parent reply other threads:[~2023-02-12 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 23:38 Jonny Grant
2023-02-12 0:14 ` Jonny Grant
2023-02-12 1:33 ` Jonathan Wakely
2023-02-12 11:20 ` Jonny Grant [this message]
2023-02-23 14:09 Saifi Khan
2023-02-23 16:32 ` Jonathan Wakely
2023-02-23 17:47 ` Saifi Khan
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=9060022e-5e3b-e85f-b9e4-9b7beb265550@jguk.org \
--to=jg@jguk.org \
--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).