public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "user202729 at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110137] implement clang -fassume-sane-operator-new Date: Wed, 05 Jun 2024 08:23:27 +0000 [thread overview] Message-ID: <bug-110137-4-Fyb1gUYy6J@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110137-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110137 --- Comment #14 from user202729 <user202729 at protonmail dot com> --- Regarding alias analysis. The current implementaion is such that: compiler | flag | can alias?| can modify global?| gcc | sane | no | no | << NEW | no-sane [default]| no | yes | clang | sane [default] | no | no | | no-sane | yes | yes | [the standard]| | no | yes | As pointed out in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110035#c13 , gcc already assume operator new's retuned pointer cannot alias any existing pointer. So no change is needed there.
next prev parent reply other threads:[~2024-06-05 8:23 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-06 8:15 [Bug c++/110137] New: " rguenth at gcc dot gnu.org 2023-06-06 8:17 ` [Bug c++/110137] " rguenth at gcc dot gnu.org 2023-06-09 12:22 ` redi at gcc dot gnu.org 2023-08-02 4:20 ` hiraditya at msn dot com 2023-08-02 6:56 ` redi at gcc dot gnu.org 2023-08-02 8:24 ` rguenther at suse dot de 2024-05-27 3:07 ` user202729 at protonmail dot com 2024-05-27 7:47 ` redi at gcc dot gnu.org 2024-06-04 10:16 ` user202729 at protonmail dot com 2024-06-04 10:39 ` hubicka at ucw dot cz 2024-06-04 11:31 ` redi at gcc dot gnu.org 2024-06-04 11:37 ` redi at gcc dot gnu.org 2024-06-04 11:45 ` jakub at gcc dot gnu.org 2024-06-04 11:57 ` Jan Hubicka 2024-06-04 11:57 ` hubicka at ucw dot cz 2024-06-05 8:23 ` user202729 at protonmail dot com [this message] 2024-06-05 13:00 ` hubicka at ucw dot cz 2024-06-23 18:14 ` user202729 at protonmail dot com
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-110137-4-Fyb1gUYy6J@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).