public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106131] -fstrict-aliasing breaks normal program that does not use any pointer or reference Date: Wed, 29 Jun 2022 02:36:41 +0000 [thread overview] Message-ID: <bug-106131-4-SJHt3yHbTp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106131-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a slightly reduced (still has std::vector in it): #include <vector> template<class A, class B> struct Pair1 { constexpr Pair1(const Pair1&) = default; constexpr Pair1(Pair1&&) = default; constexpr Pair1(const A& __a, const B& __b) : first(__a), second(__b) { } Pair1& operator=( const Pair1 & __p) { first = __p.first; second = __p.second; return *this; } A first; B second; }; typedef Pair1<int, int> Pair; std::vector<Pair> f = {{0, -11}, {0, -8}, {1, 2}}; int foo(Pair x, Pair y) { return std::max(x.second, y.second); } int main() { int t = 0; for (int J = 0; J < 1; J++) { f[J] = f[0]; if(J == 0) f[J] = f[2]; t = foo(f[J], f[1]); } if (t != 2) __builtin_abort(); }
next prev parent reply other threads:[~2022-06-29 2:36 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-29 2:05 [Bug c++/106131] New: " 18307130172 at fudan dot edu.cn 2022-06-29 2:09 ` [Bug c++/106131] " 18307130172 at fudan dot edu.cn 2022-06-29 2:36 ` pinskia at gcc dot gnu.org [this message] 2022-06-29 9:26 ` redi at gcc dot gnu.org 2022-06-29 19:20 ` [Bug c++/106131] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-06-29 19:21 ` pinskia at gcc dot gnu.org 2022-06-29 19:38 ` mpolacek at gcc dot gnu.org 2022-06-29 19:39 ` [Bug tree-optimization/106131] " mpolacek at gcc dot gnu.org 2022-06-29 19:39 ` mpolacek at gcc dot gnu.org 2022-06-30 0:50 ` 18307130172 at fudan dot edu.cn 2022-06-30 6:47 ` rguenther at suse dot de 2022-06-30 7:57 ` rguenth at gcc dot gnu.org 2022-06-30 8:31 ` rguenth at gcc dot gnu.org 2022-07-01 6:53 ` cvs-commit at gcc dot gnu.org 2022-07-01 6:54 ` [Bug tree-optimization/106131] [10/11/12 " rguenth at gcc dot gnu.org 2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org 2022-10-11 13:04 ` [Bug tree-optimization/106131] [10/11 " cvs-commit at gcc dot gnu.org 2022-10-14 10:47 ` [Bug tree-optimization/106131] [10 " cvs-commit at gcc dot gnu.org 2022-10-14 10:48 ` 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-106131-4-SJHt3yHbTp@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).