public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chenglulu at loongson dot cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114978] [14/15 regression] 548.exchange2_r 14%-28% regressions on Loongarch64 after gcc 14 snapshot 20240317 Date: Thu, 09 May 2024 02:44:40 +0000 [thread overview] Message-ID: <bug-114978-4-GKOFWNHebi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114978-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978 --- Comment #8 from chenglulu <chenglulu at loongson dot cn> --- (In reply to Chen Chen from comment #0) > We tested Loongarch64 CPU Loongson 3A6000 with "LA664" architecture in Linux > operating system AOSC OS 11.4.0 (default gcc version is 13.2.0). And we > found the 548.exchange2_r benchmark from SPEC 2017 INTrate suite suffered > significant regressions from 14% to 28% with various compiling options. > > The rate-1 results are following: > /* snip */ > > after snapshot 20240317 score 18-23.1% lower with parameters "-g -Ofast > -march=la664": > 13.2.0: "-march=la664" flag is not supported > 20240317: 11.5 (227s) > 20240324: 8.84 (296s) > 20240430: 9.43 (278s) > 14.1.0: 9.42 (278s) > /* snip */ > > > after snapshot 20240317 score 26.3-26.6% lower with parameters "-g -Ofast > -march=la464": > 13.2.0: 8.76 (299s) > 20240317: 12.8 (205s) > 20240324: 9.39 (279s) > 20240430: 9.43 (278s) > 14.1.0: 9.43 (278s) > > > 20240317: 11.5 (227s) -march=la664 > 20240317: 12.8 (205s) -march=la464 I looked for the reason for the gap between the above two results. The performance regression is caused by r14-6814. If the following modifications are made, the scores of -march=la664 and -march464 will be the same. diff --git a/gcc/config/loongarch/loongarch-def.cc b/gcc/config/loongarch/loongarch-def.cc index e8c129ce643..f27284cb20a 100644 --- a/gcc/config/loongarch/loongarch-def.cc +++ b/gcc/config/loongarch/loongarch-def.cc @@ -111,11 +111,7 @@ loongarch_rtx_cost_data::loongarch_rtx_cost_data () tune targets (i.e. -mtune=native while PRID does not correspond to any known "-mtune" type). */ array_tune<loongarch_rtx_cost_data> loongarch_cpu_rtx_cost_data = - array_tune<loongarch_rtx_cost_data> () - .set (CPU_LA664, - loongarch_rtx_cost_data () - .movcf2gr_ (COSTS_N_INSNS (1)) - .movgr2cf_ (COSTS_N_INSNS (1))); + array_tune<loongarch_rtx_cost_data> ();
next prev parent reply other threads:[~2024-05-09 2:44 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-07 17:58 [Bug fortran/114978] New: " chz0808 at gmail dot com 2024-05-07 18:12 ` [Bug fortran/114978] [14/14 regression] " sjames at gcc dot gnu.org 2024-05-07 18:13 ` xry111 at gcc dot gnu.org 2024-05-07 18:17 ` [Bug target/114978] " xry111 at gcc dot gnu.org 2024-05-07 18:18 ` xry111 at gcc dot gnu.org 2024-05-08 1:41 ` [Bug target/114978] [14/15 " chenglulu at loongson dot cn 2024-05-08 8:20 ` rguenth at gcc dot gnu.org 2024-05-08 14:41 ` chz0808 at gmail dot com 2024-05-09 2:44 ` chenglulu at loongson dot cn [this message] 2024-05-09 3:36 ` xry111 at gcc dot gnu.org 2024-05-09 3:40 ` chenglulu at loongson dot cn 2024-05-09 11:09 ` chenglulu at loongson dot cn 2024-05-09 12:57 ` chz0808 at gmail dot com 2024-05-09 13:09 ` xry111 at gcc dot gnu.org 2024-05-10 3:12 ` chz0808 at gmail dot com 2024-05-10 3:15 ` chenglulu at loongson dot cn 2024-05-15 1:24 ` chenglulu at loongson dot cn 2024-05-15 3:41 ` xry111 at gcc dot gnu.org 2024-05-15 3:57 ` chenglulu at loongson dot cn 2024-05-21 12:46 ` chenglulu at loongson dot cn 2024-05-21 12:47 ` chenglulu at loongson dot cn 2024-05-21 13:01 ` xry111 at gcc dot gnu.org 2024-05-21 13:04 ` chenglulu at loongson dot cn
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-114978-4-GKOFWNHebi@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).