From: Takayuki 'January June' Suwa <jjsuwa_sys3175@yahoo.co.jp>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Always enable LRA
Date: Sat, 15 Oct 2022 12:18:56 +0900 [thread overview]
Message-ID: <dfc6a257-d783-8a65-ad6d-5629475b3178@yahoo.co.jp> (raw)
In-Reply-To: <20221014162524.GD25951@gate.crashing.org>
On 2022/10/15 1:25, Segher Boessenkool wrote:
> On Fri, Oct 14, 2022 at 03:20:40PM +0900, Takayuki 'January June' Suwa wrote:
>> On 2022/10/14 8:56, Segher Boessenkool wrote:
>>> And finally, xtensa does
>>> /home/segher/src/gcc/libgcc/libgcc2.c:840:1: error: insn does not satisfy its constraints:
>>> 840 | }
>>> | ^
>>> (insn 8 7 9 2 (set (reg:SI 9 a9 [57])
>>> (const_int 1431655765 [0x55555555])) "/home/segher/src/gcc/libgcc/libgcc2.c":828:21 37 {movsi_internal}
>>> (expr_list:REG_EQUIV (const_int 1431655765 [0x55555555])
>>> (nil)))
>>> during RTL pass: postreload
>>> /home/segher/src/gcc/libgcc/libgcc2.c:840:1: internal compiler error: in extract_constrain_insn, at recog.cc:2692
>>
>> This is a result of knowing that Reload is tolerant of out-of-constraint constants.
>> LRA support needs to be taken care of before that, ie. in the "split1" pass.
>> Excuse me in haste.
>
> So old reload did a split itself? Or it left it to say the split2 pass?
Reload did.
[testpiece]
unsigned int test(void) {
return 0x55555555;
}
[282r.ira]
(insn 9 5 10 2 (set (reg/i:SI 2 a2)
(const_int 1431655765 [0x55555555])) "test.c":3:1 27 {movsi_internal}
(expr_list:REG_EQUAL (const_int 1431655765 [0x55555555])
(nil)))
[283r.reload]
;; Function test (test, funcdef_no=0, decl_uid=1386, cgraph_uid=1, symbol_order=0)
insn=9, live_throughout: 1, dead_or_set: 2
insn=10, live_throughout: 1, 2, dead_or_set:
Spilling for insn 9.
Reloads for insn # 9
Reload 0: reload_in (SI) = (const_int 1431655765 [0x55555555])
RL_REGS, RELOAD_FOR_INPUT (opnum = 1)
reload_in_reg: (const_int 1431655765 [0x55555555])
reload_reg_rtx: (reg/i:SI 2 a2)
deleting insn with uid = 9.
(insn 14 5 10 2 (set (reg/i:SI 2 a2)
(mem/u/c:SI (symbol_ref/u:SI ("*.LC0") [flags 0x2]) [0 S4 A32])) "test.c":3:1 27 {movsi_internal}
(nil))
prev parent reply other threads:[~2022-10-15 3:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 23:56 Segher Boessenkool
2022-10-14 0:36 ` Koning, Paul
2022-10-14 16:18 ` Segher Boessenkool
2022-10-14 16:48 ` Koning, Paul
2022-10-14 1:07 ` Jeff Law
2022-10-14 12:37 ` Koning, Paul
2022-10-14 14:38 ` Jeff Law
2022-10-14 16:37 ` Koning, Paul
2022-10-14 17:10 ` Jeff Law
2022-10-14 17:36 ` Koning, Paul
2022-10-14 21:15 ` Jeff Law
2022-10-14 21:21 ` Koning, Paul
2022-10-14 21:30 ` Jeff Law
2022-10-15 0:19 ` Jeff Law
2022-10-14 16:39 ` Richard Biener
2022-10-14 17:11 ` Jeff Law
2022-10-14 4:47 ` Jeff Law
2022-10-14 16:37 ` Segher Boessenkool
2022-10-14 17:07 ` Jeff Law
2022-10-14 17:35 ` Segher Boessenkool
2022-10-14 18:03 ` Jeff Law
2022-10-14 19:58 ` Koning, Paul
2022-10-14 20:12 ` Segher Boessenkool
2022-10-14 20:40 ` Koning, Paul
2022-10-14 6:20 ` Takayuki 'January June' Suwa
2022-10-14 16:25 ` Segher Boessenkool
2022-10-15 3:18 ` Takayuki 'January June' Suwa [this message]
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=dfc6a257-d783-8a65-ad6d-5629475b3178@yahoo.co.jp \
--to=jjsuwa_sys3175@yahoo.co.jp \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).