From: "Saifi Khan" <saifi.khan@nishan.io>
To: 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: Thu, 23 Feb 2023 14:09:53 +0000 [thread overview]
Message-ID: <20230223140953.13962.qmail@s411.sureserver.com> (raw)
Hi:
Tried Jonny Grant's example
g++ -O3 --std=c++23 -Wall -c repro_jg01.cc
With the mainline build, the code compiles without any error.
Environment
- Linux 6.1.0-3-amd64 x86_64 GNU/Linux
- Debian GLIBC 2.36-8) 2.36
- gcc version 13.0.1 20230215 (experimental) (GCC)
Curious to know, what changed in the mainline code ? Anyone knows the commit hash ?
warm regards
Saifi.
next reply other threads:[~2023-02-23 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 14:09 Saifi Khan [this message]
2023-02-23 16:32 ` Jonathan Wakely
2023-02-23 17:47 ` Saifi Khan
-- strict thread matches above, loose matches on Subject: below --
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
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=20230223140953.13962.qmail@s411.sureserver.com \
--to=saifi.khan@nishan.io \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).