From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, Vineet Gupta <vineetg@rivosinc.com>
Cc: kito.cheng@sifive.com, gcc-patches@gcc.gnu.org,
Kito Cheng <kito.cheng@gmail.com>,
Patrick O'Neill <patrick@rivosinc.com>,
Jeff Law <jlaw@ventanamicro.com>,
macro@embecosm.com, "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: Re: RISC-V Bootstrap problems
Date: Wed, 24 May 2023 21:43:30 -0600 [thread overview]
Message-ID: <66780d8b-41bf-95ac-3266-c4025636757e@gmail.com> (raw)
In-Reply-To: <mhng-bb03bb89-235e-4658-9cdf-76626eacbe97@palmer-ri-x1c9a>
On 5/24/23 17:13, Palmer Dabbelt wrote:
> On Wed, 24 May 2023 16:12:20 PDT (-0700), Vineet Gupta wrote:
[ ... big snip ... ]
>>
>> Never mind. Looks like I found the issue - with just trial and error and
>> no idea of how this stuff works.
>> The torture-{init,finish} needs to be in riscv.exp not rvv.exp
>> Running full tests now.
>
> Thanks!
Marginally related. I was able to bisect the "hang" when 3-staging the
trunk on RISC-V with qemu user mode emulation.
So it wasn't actually hanging, but after the introduction of segment
intrinsics the compilation time for insn-emit explodes -- previously I
could do a full 3-stage bootstrap, build the glibc & the kernel, then
test c/c++/fortran in ~10 hours.
Now just building insn-emit.o alone takes ~10 hours in that environment.
I suspect (but have not yet confirmed) that we should see a huge
compile-time spike in cross builds as well, though obviously it won't be
as bad since we're not using qemu emulation.
Clearly something isn't scaling well. I don't know if we've got a crazy
large function in there, a crazy number of functions or something that's
just triggering a compile-time scaling problem. Whatever it is, we
probably need to address it.
jeff
next prev parent reply other threads:[~2023-05-25 3:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 6:41 [PATCH] RISC-V: Add missing torture-init and torture-finish for rvv.exp Kito Cheng
2023-05-22 9:17 ` Kito Cheng
2023-05-23 3:52 ` Vineet Gupta
2023-05-24 18:18 ` Vineet Gupta
2023-05-24 20:34 ` Thomas Schwinge
2023-05-24 22:13 ` Vineet Gupta
2023-05-24 23:12 ` Vineet Gupta
2023-05-24 23:13 ` Palmer Dabbelt
2023-05-25 3:43 ` Jeff Law [this message]
2023-05-25 3:46 ` Re: RISC-V Bootstrap problems juzhe.zhong
2023-05-25 3:53 ` Kito Cheng
2023-05-25 3:54 ` juzhe.zhong
2023-05-25 4:07 ` Jeff Law
2023-05-25 4:19 ` juzhe.zhong
2023-05-25 13:55 ` Jeff Law
2023-05-25 4:06 ` Jeff Law
2023-05-25 4:08 ` Kito Cheng
2023-05-25 3:51 ` juzhe.zhong
2023-05-24 23:15 ` [PATCH] RISC-V: Add missing torture-init and torture-finish for rvv.exp Jeff Law
2023-05-25 20:26 ` Thomas Schwinge
2023-05-26 23:38 ` Vineet Gupta
2023-05-30 18:43 ` Vineet Gupta
2023-05-31 16:28 ` Vineet Gupta
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=66780d8b-41bf-95ac-3266-c4025636757e@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=macro@embecosm.com \
--cc=palmer@dabbelt.com \
--cc=patrick@rivosinc.com \
--cc=vineetg@rivosinc.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).