public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vlad at solidsands dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/111773] Inconsistent optimization of replaced operator new() Date: Wed, 18 Oct 2023 14:09:05 +0000 [thread overview] Message-ID: <bug-111773-4-KVT3FAQPKU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111773 --- Comment #6 from Vlad Yaglamunov <vlad at solidsands dot nl> --- I agree with Richard's explanation. Seems like my first example is an undefined behavior. In section [basic.stc.dynamic.allocation] par 2, in C++17, was added the following: "Furthermore, for the library allocation functions in [new.delete.single] and [new.delete.array], p0 shall represent the address of a block of storage disjoint from the storage for any other object accessible to the caller."
next prev parent reply other threads:[~2023-10-18 14:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-11 15:59 [Bug c++/111773] New: " vlad at solidsands dot nl 2023-10-11 16:05 ` [Bug c++/111773] " pinskia at gcc dot gnu.org 2023-10-12 8:15 ` [Bug ipa/111773] " rguenth at gcc dot gnu.org 2023-10-12 8:48 ` sjames at gcc dot gnu.org 2023-10-13 6:34 ` cvs-commit at gcc dot gnu.org 2023-10-13 6:43 ` rguenth at gcc dot gnu.org 2023-10-18 14:09 ` vlad at solidsands dot nl [this message] 2023-10-19 6:16 ` rguenth at gcc dot gnu.org
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=bug-111773-4-KVT3FAQPKU@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).