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] New: LoongArch: Alignments in tune parameters are not precise and they regress performance
Date: Fri, 08 Dec 2023 11:44:25 +0000 [thread overview]
Message-ID: <bug-112919-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
Bug ID: 112919
Summary: LoongArch: Alignments in tune parameters are not
precise and they regress performance
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: xry111 at gcc dot gnu.org
Target Milestone: ---
In r14-1839 we added -falign-function=32 -falign-label=16 for LA464. But these
values is not precise now because in r14-4674 we removed
ASM_OUTPUT_ALIGN_WITH_NOP and altered the semantics of -falign-* switches. And
we also have LA664 now which may benefit from a different value.
next reply other threads:[~2023-12-08 11:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 11:44 xry111 at gcc dot gnu.org [this message]
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
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@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: link
Be 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).