public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95638] Legit-looking code doesn't work with -O2 Date: Thu, 11 Jun 2020 15:40:36 +0000 [thread overview] Message-ID: <bug-95638-4-0RM9D2zGFv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95638-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95638 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- I don't see anything obviously wrong with the code. Nothing seems to write to the storage before the constructor, let alone rely on those writes being preserved.
next prev parent reply other threads:[~2020-06-11 15:40 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-11 11:45 [Bug c++/95638] New: " officesamurai at gmail dot com 2020-06-11 12:08 ` [Bug c++/95638] " jakub at gcc dot gnu.org 2020-06-11 12:12 ` marxin at gcc dot gnu.org 2020-06-11 12:23 ` jakub at gcc dot gnu.org 2020-06-11 15:40 ` redi at gcc dot gnu.org [this message] 2020-06-12 1:17 ` amker at gcc dot gnu.org 2020-06-12 7:20 ` [Bug c++/95638] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-06-14 0:47 ` amker at gcc dot gnu.org 2020-06-20 7:56 ` [Bug tree-optimization/95638] " cvs-commit at gcc dot gnu.org 2020-06-29 10:07 ` jakub at gcc dot gnu.org 2020-06-29 12:10 ` amker at gcc dot gnu.org 2020-07-09 11:47 ` rguenth at gcc dot gnu.org 2020-07-09 11:48 ` [Bug tree-optimization/95638] [10 " rguenth at gcc dot gnu.org 2020-07-10 3:59 ` cvs-commit at gcc dot gnu.org 2020-07-10 4:12 ` cvs-commit at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-07-23 7:11 ` amker at gcc dot gnu.org 2021-03-27 2:44 ` amker 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-95638-4-0RM9D2zGFv@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).