From: Xi Ruoyao <xry111@mengyan1223.wang>
To: Paul Hua <paul.hua.gm@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
chenglulu@loongson.cn, Chenghua Xu <xuchenghua@loongson.cn>,
yangyujie@loongson.cn, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3 06/12] LoongArch Port: Builtin macros.
Date: Mon, 20 Dec 2021 15:35:31 +0800 [thread overview]
Message-ID: <1394258f26e6741c9adbfe36cb12bc1c58f1e1d4.camel@mengyan1223.wang> (raw)
In-Reply-To: <CAKjxQHmzg1+bYtEQTqZebmGjJqP2LEGYT0MGrMFkAinFiz8Twg@mail.gmail.com>
Hi,
I've bootstraped the patch with my GNU-stack fix
(https://github.com/loongson/gcc/pull/62) and --enable-werror-always.
Bootstrap succeeded, but with some warnings:
../../gcc/config/loongarch/loongarch.md:3205:1: warning: operand 0 missing mode?
../../gcc/config/loongarch/loongarch.md:3282:1: warning: operand 1 missing mode?
../../gcc/config/loongarch/loongarch.md:3329:1: warning: operand 1 missing mode?
../../gcc/config/loongarch/loongarch.md:3392:1: warning: operand 0 missing mode?
../../gcc/config/loongarch/loongarch.md:3470:1: warning: operand 1 missing mode?
../../gcc/config/loongarch/loongarch.md:3520:1: warning: operand 1 missing mode?
A similar issue exists for MIPS (PR101593) and I've not figured out how
to silence these warnings.
I'm trying to run GCC regression test on LoongArch, but all my previous
tries couldn't finish because a kernel panic was triggered. The kernel
was built from source pulled from
https://github.com/loongson/linux/tree/loongarch-next.
I'm not sure if this is a bug in Huacai's patches, or a bug in mainline
kernel, or even a hardware issue. If you have some idea about the panic
please inform me (this is off-topic though).
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2021-12-20 7:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 7:43 [PATCH v3 00/12] Add LoongArch support Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 01/12] LoongArch Port: gcc build Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 02/12] LoongArch Port: Regenerate gcc/configure Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 03/12] LoongArch Port: Machine Decsription files Chenghua Xu
2021-12-20 12:34 ` Xi Ruoyao
2021-12-10 7:43 ` [PATCH v3 04/12] LoongArch Port: Machine description C files and .h files Chenghua Xu
2021-12-18 17:53 ` Xi Ruoyao
2021-12-10 7:43 ` [PATCH v3 05/12] LoongArch Port: Builtin functions Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 06/12] LoongArch Port: Builtin macros Chenghua Xu
2021-12-14 0:13 ` Joseph Myers
2021-12-17 7:45 ` Paul Hua
2021-12-18 9:37 ` Xi Ruoyao
2021-12-19 1:31 ` Paul Hua
2021-12-20 7:35 ` Xi Ruoyao [this message]
2021-12-20 14:08 ` Xi Ruoyao
2021-12-10 7:43 ` [PATCH v3 07/12] LoongArch Port: libgcc Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 08/12] LoongArch Port: Regenerate libgcc/configure Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 09/12] LoongArch Port: libgomp Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 10/12] LoongArch Port: gcc/testsuite Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 11/12] LoongArch Port: Regenerate configure Chenghua Xu
2021-12-10 7:43 ` [PATCH v3 12/12] LoongArch Port: Add doc Chenghua Xu
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=1394258f26e6741c9adbfe36cb12bc1c58f1e1d4.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=paul.hua.gm@gmail.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).