From: Xi Ruoyao <xry111@xry111.site>
To: chenglulu <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH v2 2/2] LoongArch: When the code model is extreme, the symbol address is obtained through macro instructions regardless of the value of -mexplicit-relocs.
Date: Fri, 12 Jan 2024 19:42:11 +0800 [thread overview]
Message-ID: <7808ffa81093a41202b1a5c3cf12b76482741b1e.camel@xry111.site> (raw)
In-Reply-To: <b195b865-de49-a0ab-d8f8-88195c1660cb@loongson.cn>
在 2024-01-12星期五的 09:46 +0800，chenglulu写道：
> > I found an issue bootstrapping GCC with -mcmodel=extreme in BOOT_CFLAGS:
> > we need a target hook to tell the generic code
> > UNSPEC_LA_PCREL_64_PART{1,2} are just a wrapper around symbols, or we'll
> > see millions lines of messages like
> >
> > ../../gcc/gcc/tree.h:4171:1: note: non-delegitimized UNSPEC
> > UNSPEC_LA_PCREL_64_PART1 (42) found in variable location
>
> I build GCC with -mcmodel=extreme in BOOT_CFLAGS, but I haven't reproduced the problem you mentioned.
>
> $ ../configure --host=loongarch64-linux-gnu --target=loongarch64-linux-gnu --build=loongarch64-linux-gnu \
> --with-arch=loongarch64 --with-abi=lp64d --enable-tls --enable-languages=c,c++,fortran,lto --enable-plugin \
> --disable-multilib --disable-host-shared --enable-bootstrap --enable-checking=release
> $ make BOOT_FLAGS="-mcmodel=extreme"
>
> What did I do wrong?:-(
BOOT_CFLAGS, not BOOT_FLAGS :).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-01-12 11:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 3:40 [PATCH v2 0/2] When cmodel=extreme, add macro support and only support macros Lulu Cheng
2024-01-05 3:40 ` [PATCH v2 1/2] LoongArch: Add the macro implementation of mcmodel=extreme Lulu Cheng
2024-01-05 3:40 ` [PATCH v2 2/2] LoongArch: When the code model is extreme, the symbol address is obtained through macro instructions regardless of the value of -mexplicit-relocs Lulu Cheng
2024-01-05 8:37 ` Xi Ruoyao
2024-01-05 8:51 ` chenglulu
2024-01-05 9:57 ` chenglulu
2024-01-05 10:25 ` Xi Ruoyao
2024-01-05 11:55 ` Xi Ruoyao
2024-01-05 12:45 ` chenglulu
2024-01-05 14:16 ` Xi Ruoyao
2024-01-12 1:46 ` chenglulu
2024-01-12 11:42 ` Xi Ruoyao [this message]
2024-01-13 7:01 ` chenglulu
2024-01-13 13:05 ` Xi Ruoyao
2024-01-13 14:05 ` chenglulu
2024-01-17 9:38 ` chenglulu
2024-01-17 9:50 ` Xi Ruoyao
2024-01-17 9:57 ` chenglulu
2024-01-19 5:46 ` Xi Ruoyao
2024-01-19 8:51 ` chenglulu
2024-01-22 7:27 ` chenglulu
2024-01-23 19:36 ` Xi Ruoyao
2024-01-25 0:48 ` chenglulu
2024-01-25 7:59 ` Xi Ruoyao
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=7808ffa81093a41202b1a5c3cf12b76482741b1e.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xuchenghua@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).