public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97960] [8/9/10/11 Regression] Wrong code at -O3 since r8-6511-g3ae129323d Date: Mon, 23 Nov 2020 17:53:58 +0000 [thread overview] Message-ID: <bug-97960-4-API7Oy4yqI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97960-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97960 --- Comment #1 from Alex Coplan <acoplan at gcc dot gnu.org> --- C testcase: const int *c(const int *p, const int *q) { if (*p < *q) return q; return p; } short a[575]; unsigned b[25]; unsigned char g; int main() { for (int e = 0; e < 23; ++e) a[e * 23] = 16137; int t1 = g; int t2 = 253; signed char h = *c(&t1, &t2) + 3; for (; h < 24; h++) b[h] = 1064739102; for (int e = 0; e < 23; ++e) if (a[e * 23] != 16137) __builtin_abort(); }
next prev parent reply other threads:[~2020-11-23 17:53 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-23 17:13 [Bug tree-optimization/97960] New: " acoplan at gcc dot gnu.org 2020-11-23 17:53 ` acoplan at gcc dot gnu.org [this message] 2020-11-23 17:55 ` [Bug tree-optimization/97960] " marxin at gcc dot gnu.org 2020-11-24 8:20 ` rguenth at gcc dot gnu.org 2020-11-24 15:12 ` rguenth at gcc dot gnu.org 2020-11-24 15:29 ` rsandifo at gcc dot gnu.org 2021-01-21 11:59 ` jakub at gcc dot gnu.org 2021-01-22 8:01 ` rguenth at gcc dot gnu.org 2021-01-22 9:27 ` acoplan at gcc dot gnu.org 2021-02-01 16:53 ` jakub at gcc dot gnu.org 2021-02-02 9:03 ` cvs-commit at gcc dot gnu.org 2021-02-02 9:35 ` [Bug tree-optimization/97960] [8/9/10 " jakub at gcc dot gnu.org 2021-04-22 13:27 ` rsandifo at gcc dot gnu.org 2021-04-23 9:21 ` rsandifo 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-97960-4-API7Oy4yqI@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).