From: Lehua Ding <lehua.ding@rivai.ai>
To: Dimitar Dimitrov <dimitar@dinux.eu>
Cc: gcc-patches@gcc.gnu.org, vmakarov@redhat.com,
richard.sandiford@arm.com, juzhe.zhong@rivai.ai
Subject: Re: [PATCH 0/7] ira/lra: Support subreg coalesce
Date: Fri, 10 Nov 2023 16:46:21 +0800 [thread overview]
Message-ID: <A7DDAC8495FCB814+b31e2ee5-7429-4004-a948-cadb862f5e3c@rivai.ai> (raw)
In-Reply-To: <ZUu9v8dUUf8FD8EM@kendros>
Hi Dimitar,
Thanks for the tests.
> This patch set breaks the build for at least three embedded targets. See
> below.
>
> For avr the GCC build fails with:
> /mnt/nvme/dinux/local-workspace/gcc/gcc/ira-lives.cc:149:39: error: call of overloaded ‘set_subreg_conflict_hard_regs(ira_allocno*&, int&)’ is ambiguous
> 149 | set_subreg_conflict_hard_regs (OBJECT_ALLOCNO (obj), regno);
I think it's because `HARD_REG_SET` and `unsigned int` are of the same
type on avr target(i.e. No more than 32 registers on avr target), so
these two bellow function prototypes conflict, I'll adjust it.
static void
set_subreg_conflict_hard_regs (ira_allocno_t a, HARD_REG_SET regs)
static void
set_subreg_conflict_hard_regs (ira_allocno_t a, unsigned int regno)
> For arm-none-eabi the newlib build fails with:
> /mnt/nvme/dinux/local-workspace/newlib/newlib/libm/math/e_jn.c:279:1: internal compiler error: Floating point exception
> 279 | }
> | ^
> 0x1176e0f crash_signal
> /mnt/nvme/dinux/local-workspace/gcc/gcc/toplev.cc:316
> 0xf6008d get_range_hard_regs(int, subreg_range const&)
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:609
> 0xf6008d get_range_hard_regs(int, subreg_range const&)
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:601
> 0xf60312 new_insn_reg
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:658
> 0xf6064d add_regs_to_insn_regno_info
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1623
> 0xf62909 lra_update_insn_regno_info(rtx_insn*)
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1769
> 0xf62e46 lra_update_insn_regno_info(rtx_insn*)
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1762
> 0xf62e46 lra_push_insn_1
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1919
> 0xf62f2d lra_push_insn(rtx_insn*)
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1927
> 0xf62f2d push_insns
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1970
> 0xf63302 push_insns
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:1966
> 0xf63302 lra(_IO_FILE*)
> /mnt/nvme/dinux/local-workspace/gcc/gcc/lra.cc:2511
> 0xf0e399 do_reload
> /mnt/nvme/dinux/local-workspace/gcc/gcc/ira.cc:5960
> 0xf0e399 execute
> /mnt/nvme/dinux/local-workspace/gcc/gcc/ira.cc:6148
>
> The divide by zero error above is interesting. I'm not sure why ira_reg_class_max_nregs[] yields 0 for the pseudo register 168 in the following rtx:
> (debug_insn 168 167 169 19 (var_location:SI encoding (reg/v:SI 168 [ encoding ])) -1
> (nil))
I just cross compiled an arm-none-eabi compiler and didn't encounter
this error, can you give me a little more config info about build? For
example, flags_for_target, etc. Thanks again.
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
next prev parent reply other threads:[~2023-11-10 8:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 3:47 Lehua Ding
2023-11-08 3:47 ` [PATCH 1/7] ira: Refactor the handling of register conflicts to make it more general Lehua Ding
2023-11-08 7:57 ` Richard Biener
2023-11-08 8:34 ` Lehua Ding
2023-11-08 3:47 ` [PATCH 2/7] ira: Add live_subreg problem and apply to ira pass Lehua Ding
2023-11-08 3:47 ` [PATCH 3/7] ira: Support subreg live range track Lehua Ding
2023-11-08 3:47 ` [PATCH 4/7] ira: Support subreg copy Lehua Ding
2023-11-08 3:47 ` [PATCH 5/7] ira: Add all nregs >= 2 pseudos to tracke subreg list Lehua Ding
2023-11-08 3:47 ` [PATCH 6/7] lra: Apply live_subreg df_problem to lra pass Lehua Ding
2023-11-08 3:47 ` [PATCH 7/7] lra: Support subreg live range track and conflict detect Lehua Ding
2023-11-08 3:55 ` [PATCH 0/7] ira/lra: Support subreg coalesce juzhe.zhong
2023-11-10 9:29 ` Lehua Ding
2023-11-08 9:40 ` Richard Sandiford
2023-11-08 19:13 ` Jeff Law
2023-11-10 9:43 ` Lehua Ding
2023-11-11 15:33 ` Richard Sandiford
2023-11-11 17:46 ` Jeff Law
2023-11-12 1:16 ` 钟居哲
2023-11-12 11:53 ` Richard Sandiford
2023-11-13 1:11 ` juzhe.zhong
2023-11-13 3:34 ` Lehua Ding
2023-11-10 9:26 ` Lehua Ding
2023-11-10 10:16 ` Richard Sandiford
2023-11-10 10:30 ` Lehua Ding
2023-11-10 10:39 ` Richard Sandiford
2023-11-10 14:28 ` Jeff Law
2023-11-08 16:56 ` Dimitar Dimitrov
2023-11-10 8:46 ` Lehua Ding [this message]
2023-11-10 8:53 ` Lehua Ding
2023-11-10 16:00 ` Dimitar Dimitrov
2023-11-12 6:06 ` Lehua Ding
2023-11-12 10:08 ` Lehua Ding
2023-11-09 20:24 ` Vladimir Makarov
2023-11-10 7:59 ` Richard Biener
2023-11-12 12:01 ` Lehua Ding
2023-11-12 12:12 ` Lehua Ding
2023-11-13 19:25 ` Vladimir Makarov
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=A7DDAC8495FCB814+b31e2ee5-7429-4004-a948-cadb862f5e3c@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=dimitar@dinux.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=richard.sandiford@arm.com \
--cc=vmakarov@redhat.com \
/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).