public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98213] [11 Regression] Never ending compilation at -O3 since r11-161-g283cb9ea6293e813 Date: Wed, 09 Dec 2020 13:00:20 +0000 [thread overview] Message-ID: <bug-98213-4-U1yHmxjgyo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98213-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98213 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Sure: long var_23, min___a; int var_24, test_var_8, test_arr_16; extern bool arr_20[][13]; char arr_21_0_0_0_0_0; const unsigned long long &min(unsigned long long &__b) { if (__b) return __b; return min___a; } const unsigned long long &max(const unsigned long long &__a, const unsigned long long &__b) { if (__b) return __b; return __a; } int *test_arr_0; unsigned long long test_var_1; void test() { for (;;) { for (int i_6 = 0; i_6 < 19; i_6 += 4) for (long i_7(test_var_8); i_7; i_7 += 2) { arr_20[0][i_7] = arr_21_0_0_0_0_0 = 0; var_23 = test_arr_0[0]; } const unsigned long long &__trans_tmp_1 = min(test_var_1); var_24 = max(test_arr_16, __trans_tmp_1); } }
next prev parent reply other threads:[~2020-12-09 13:00 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-09 10:46 [Bug tree-optimization/98213] New: " marxin at gcc dot gnu.org 2020-12-09 10:46 ` [Bug tree-optimization/98213] " marxin at gcc dot gnu.org 2020-12-09 12:45 ` rguenth at gcc dot gnu.org 2020-12-09 13:00 ` marxin at gcc dot gnu.org [this message] 2020-12-09 14:37 ` rguenth at gcc dot gnu.org 2020-12-09 16:27 ` cvs-commit at gcc dot gnu.org 2020-12-09 16:27 ` 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-98213-4-U1yHmxjgyo@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).