From: Xi Ruoyao <xry111@xry111.site>
To: Yang Yujie <yangyujie@loongson.cn>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: gcc-patches@gcc.gnu.org, chenglulu@loongson.cn,
richard.sandiford@arm.com, xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: Reimplement multilib build option handling.
Date: Sat, 07 Oct 2023 15:08:34 +0800 [thread overview]
Message-ID: <2a29d0fc529af520c65acb0f1e295055525c4ff0.camel@xry111.site> (raw)
In-Reply-To: <qok5yr2z223vcw7xliucxgaafgdh5abv2dfn2jxzyrwjg6lks7@3vfmihcumjsk>
On Sat, 2023-10-07 at 11:41 +0800, Yang Yujie wrote:
> Thanks for the testing!
>
> This error seems to be difficult to reproduce since it is a makefile dependency
> problem. I think appending loongarch-multilib.h to $(GTM_H) instead of $(TM_H)
> could help.
FWIW such issues are easier to reproduce with a high -j number. I can
easily reproduce it with -j32 on a 3C5000-based server.
> > And when this is fixed, it might be a nice idea to have a
> > --with-multilib-list config in ./contrib/config-list.mk .
>
> Thanks, will add this later too.
>
> P.S. Currently support for "f32" is not active, and it should probably be
> avoided if you want to build a working rootfs.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-10-07 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 9:52 Yang Yujie
2023-09-15 2:44 ` [pushed][PATCH] " chenglulu
2023-10-04 12:13 ` [PATCH] " Jan-Benedict Glaw
2023-10-07 3:41 ` Yang Yujie
2023-10-07 7:08 ` Xi Ruoyao [this message]
2023-10-07 8:03 ` Jan-Benedict Glaw
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=2a29d0fc529af520c65acb0f1e295055525c4ff0.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=richard.sandiford@arm.com \
--cc=xuchenghua@loongson.cn \
--cc=yangyujie@loongson.cn \
/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).