public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Mon, 08 Apr 2024 01:04:31 +0000 [thread overview] Message-ID: <bug-112919-4-1hq0S5eySF@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 --- Comment #22 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by LuluCheng <chenglulu@gcc.gnu.org>: https://gcc.gnu.org/g:8f0ff6b998748f3581e0f06e3108193866b1209d commit r14-9824-g8f0ff6b998748f3581e0f06e3108193866b1209d Author: Lulu Cheng <chenglulu@loongson.cn> Date: Tue Apr 2 14:29:08 2024 +0800 LoongArch: Set default alignment for functions jumps and loops [PR112919]. Xi Ruoyao set the alignment rules under LA464 in commit r14-1839, but the macro ASM_OUTPUT_ALIGN_WITH_NOP was removed in R14-4674, which affected the alignment rules. So I set different aligns on LA464 and LA664 again to test the performance of spec2006, and modify the alignment based on the test results. gcc/ChangeLog: PR target/112919 * config/loongarch/loongarch-def.cc (la664_align): Newly defined function that sets alignment rules under the LA664 microarchitecture. * config/loongarch/loongarch-opts.cc (loongarch_target_option_override): If not optimizing for size, set the default alignment to what the target wants. * config/loongarch/loongarch-tune.h (struct loongarch_align): Add new member variables jump and loop.
next prev parent reply other threads:[~2024-04-08 1:04 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 ` [Bug target/112919] " xry111 at gcc dot gnu.org 2023-12-09 17:52 ` 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 [this message] 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-1hq0S5eySF@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).