public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95798] [10/11 Regression] Initialization code --- suboptimal Date: Mon, 22 Jun 2020 10:42:10 +0000 [thread overview] Message-ID: <bug-95798-4-AuHYRvUR9B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95798-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95798 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Summary|Initialization code --- |[10/11 Regression] |suboptimal |Initialization code --- | |suboptimal Last reconfirmed| |2020-06-22 CC| |jakub at gcc dot gnu.org, | |rdapp at gcc dot gnu.org Target Milestone|--- |10.2 Ever confirmed|0 |1 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The 9 -> 10 regression started with r10-2806-gdf7d46d925c7baca7bf9961aee900876d8aef225 since which the IL is much larger and the resulting code less efficient. The testcase as written is just weird, it is an expensive check whether the program is called with multiple of 128 arguments >= 1024 arguments (otherwise it invokes UB). Adjusted testcase that is more meaningful: void bar (unsigned long long *, int); void foo (int y, unsigned long long z) { unsigned long long x[1024]; unsigned long long i = y % 127; __builtin_memset (x, -1, sizeof (x)); x[i] = 0; x[i + 1] = 0; x[i + 2] = 0; x[i + 3] = 0; x[i + 4] = 0; x[i + 5] = 0; x[i + 6] = 0; x[i + 7] = 0; bar (x, y); }
next prev parent reply other threads:[~2020-06-22 10:42 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-21 7:16 [Bug target/95798] New: " zero at smallinteger dot com 2020-06-21 16:57 ` [Bug target/95798] " zero at smallinteger dot com 2020-06-22 10:42 ` jakub at gcc dot gnu.org [this message] 2020-06-22 10:44 ` [Bug target/95798] [10/11 Regression] " jakub at gcc dot gnu.org 2020-06-22 13:05 ` jakub at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-10-12 12:54 ` rguenth at gcc dot gnu.org 2021-02-24 15:33 ` jakub at gcc dot gnu.org 2021-02-25 9:26 ` cvs-commit at gcc dot gnu.org 2021-02-25 9:27 ` [Bug target/95798] [10 " jakub at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 8:55 ` 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-95798-4-AuHYRvUR9B@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).