public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dizhao at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114513] [aarch64] floating-point registers are used when GPRs are preferred
Date: Thu, 28 Mar 2024 09:17:41 +0000 [thread overview]
Message-ID: <bug-114513-4-2Ds6i4gWfu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114513-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114513
--- Comment #1 from Di Zhao <dizhao at os dot amperecomputing.com> ---
I've debugged this a bit. From dump file 311r.sched1, the problem seems to have
something to do with floatunsdidf2. After processing this instruction, the
costs of FP_REGS became 0. (r=107 is "b")
Processing insn 31 {floatunsdidf2} (freq=69)
31: r111:DF=uns_float(r107:DI)
REG_DEAD r107:DI
Alt 0: (0) =w (1) w
op 0(r=111) new costs MEM:276 POINTER_AND_FP_REGS:345 FP_REGS:0
FP_LO_REGS:0 FP_LO8_REGS:0 GENERAL_REGS:345 STUB_REGS:345
TAILCALL_ADDR_REGS:345 W12_W15_REGS:345 W8_W11_REGS:345
op 1(r=107) new costs MEM:276 POINTER_AND_FP_REGS:345 FP_REGS:0
FP_LO_REGS:0 FP_LO8_REGS:0 GENERAL_REGS:345 STUB_REGS:345
TAILCALL_ADDR_REGS:345 W12_W15_REGS:345 W8_W11_REGS:345
Alt 1: (0) w (1) ?r
op 1(r=107) new costs GENERAL_REGS:138 STUB_REGS:138
TAILCALL_ADDR_REGS:138 W12_W15_REGS:138 W8_W11_REGS:138
Final costs after insn 31 {floatunsdidf2} (freq=69)
31: r111:DF=uns_float(r107:DI)
REG_DEAD r107:DI
op 0(r=111) MEM:276(+276) POINTER_AND_FP_REGS:345(+345) FP_REGS:0(+0)
FP_LO_REGS:0(+0) FP_LO8_REGS:0(+0) GENERAL_REGS:345(+345) STUB_REGS:345(+345)
TAILCALL_ADDR_REGS:345(+345) W12_W15_REGS:345(+345) W8_W11_REGS:345(+345)
op 1(r=107) MEM:9861(+276) POINTER_AND_FP_REGS:17631(+345)
FP_REGS:0(+0) FP_LO_REGS:0(+0) FP_LO8_REGS:0(+0) GENERAL_REGS:138(+138)
STUB_REGS:138(+138) TAILCALL_ADDR_REGS:138(+138) W12_W15_REGS:138(+138)
W8_W11_REGS:138(+138)
next prev parent reply other threads:[~2024-03-28 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 9:10 [Bug rtl-optimization/114513] New: " dizhao at os dot amperecomputing.com
2024-03-28 9:17 ` dizhao at os dot amperecomputing.com [this message]
2024-03-28 21:55 ` [Bug target/114513] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-03-28 22:01 ` pinskia at gcc dot gnu.org
2024-03-29 23:47 ` law at gcc dot gnu.org
2024-04-18 10:51 ` tnfchris 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-114513-4-2Ds6i4gWfu@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).