public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yangyang305 at huawei dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97760] New: GCC outputs wrong values when compiling the testcase with -O3 Date: Mon, 09 Nov 2020 02:58:48 +0000 [thread overview] Message-ID: <bug-97760-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97760 Bug ID: 97760 Summary: GCC outputs wrong values when compiling the testcase with -O3 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: yangyang305 at huawei dot com Target Milestone: --- Hi, gcc-trunk outputs wrong values when compiling the attached testcase with -O3. gcc -O0 test.c -w && ./a.out 159,150,150 150 gcc -O3 test.c -w && ./a.out 159,123,123 123 GCC version: 11.0.0 20201106 (experimental)
next reply other threads:[~2020-11-09 2:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-09 2:58 yangyang305 at huawei dot com [this message] 2020-11-09 3:01 ` [Bug tree-optimization/97760] " yangyang305 at huawei dot com 2020-11-09 8:13 ` [Bug tree-optimization/97760] [10/11 Regression] GCC outputs wrong values when compiling the testcase with -O3 since r10-4200-gb7ff7cef5005721e marxin at gcc dot gnu.org 2020-11-09 8:17 ` rguenth at gcc dot gnu.org 2020-11-09 13:38 ` rguenth at gcc dot gnu.org 2020-11-09 14:19 ` rguenth at gcc dot gnu.org 2020-11-10 9:18 ` cvs-commit at gcc dot gnu.org 2020-11-10 9:22 ` [Bug tree-optimization/97760] [10 " rguenth at gcc dot gnu.org 2020-12-01 15:44 ` cvs-commit at gcc dot gnu.org 2020-12-01 15:45 ` 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-97760-4@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).