public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112919] LoongArch: Alignments in tune parameters are not precise and they regress performance Date: Fri, 08 Dec 2023 12:03:45 +0000 [thread overview] Message-ID: <bug-112919-4-aNfI7erRt1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112919-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919 Xi Ruoyao <xry111 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://github.com/loongson | |-community/discussions/issu | |es/23 CC| |chenglulu at loongson dot cn, | |xen0n at gentoo dot org Target| |loongarch64-*-* --- Comment #1 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- Jia Jie reported a huge performance regression running Coremarks from GCC 13 to 14, and I can confirm it on LA664. It seems a part of the regression is caused by over-aligning the labels. On a LA664 with different configurations I get Coremarks Iterations/Sec values (the larger the better): 21120 with GCC 13.2.0 18320 with GCC 14.0.0 (with the default: -falign-labels=16 -falign-functions=32) 19972 with GCC 14.0.0 + -falign-loops=32 -falign-labels=4 -falign-jumps=4 -falign-functions=32 (the best I've got) 19938 with GCC 14.0.0 + -falign-loops=32 -falign-labels=4 -falign-jumps=4 -falign-functions=16 19964 with GCC 14.0.0 + -falign-loops=32 -falign-labels=4 -falign-jumps=4 -falign-functions=64 19276 with GCC 14.0.0 + -falign-loops=32 -falign-labels=8 -falign-jumps=4 -falign-functions=32 19674 with GCC 14.0.0 + -falign-loops=32 -falign-labels=4 -falign-jumps=8 -falign-functions=32 19752 with GCC 14.0.0 + -falign-loops=16 -falign-labels=4 -falign-jumps=4 -falign-functions=32 19922 with GCC 14.0.0 + -falign-loops=64 -falign-labels=4 -falign-jumps=4 -falign-functions=32 Lulu: can you help to run some other benchmarks like SPEC (I don't have an access to it) and update these values for LA464 and LA664?
next prev parent reply other threads:[~2023-12-08 12:03 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-08 11:44 [Bug target/112919] New: " xry111 at gcc dot gnu.org 2023-12-08 12:03 ` xry111 at gcc dot gnu.org [this message] 2023-12-09 17:52 ` [Bug target/112919] " xry111 at gcc dot gnu.org 2023-12-10 16:46 ` xry111 at gcc dot gnu.org 2023-12-10 18:25 ` xry111 at gcc dot gnu.org 2023-12-12 1:55 ` chenglulu at loongson dot cn 2024-01-16 6:38 ` chenglulu at loongson dot cn 2024-02-01 16:51 ` xry111 at gcc dot gnu.org 2024-02-02 1:08 ` chenglulu at loongson dot cn 2024-03-01 7:51 ` xry111 at gcc dot gnu.org 2024-03-01 8:14 ` chenglulu at loongson dot cn 2024-03-01 8:25 ` xry111 at gcc dot gnu.org 2024-03-01 8:49 ` chenglulu at loongson dot cn 2024-03-06 8:33 ` chenglulu at loongson dot cn 2024-03-06 9:12 ` chenglulu at loongson dot cn 2024-03-07 11:09 ` xry111 at gcc dot gnu.org 2024-03-07 11:30 ` chenglulu at loongson dot cn 2024-03-26 1:57 ` chenglulu at loongson dot cn 2024-03-27 12:57 ` xry111 at gcc dot gnu.org 2024-03-27 13:54 ` chenglulu at loongson dot cn 2024-04-01 13:22 ` xry111 at gcc dot gnu.org 2024-04-01 13:36 ` chenglulu at loongson dot cn 2024-04-08 1:04 ` cvs-commit at gcc dot gnu.org 2024-04-08 12:25 ` xry111 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-112919-4-aNfI7erRt1@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).