From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH v1] LoongArch: Add support code model extreme.
Date: Thu, 18 Aug 2022 21:00:27 +0800 [thread overview]
Message-ID: <524ce281-032e-4988-13c5-da8377d4246a@loongson.cn> (raw)
In-Reply-To: <f5a123c2059f2d8642861bf55d248f249f9982c2.camel@xry111.site>
在 2022/8/18 下午8:52, Xi Ruoyao 写道:
> On Thu, 2022-08-18 at 19:49 +0800, Lulu Cheng wrote:
>>> I think we can ignore the effect of -fplt if code model is extreme,
>>> instead of forcing everyone to explicitly add -fno-plt. The "large"
>>> code model of x86_64 also does not limit the address range and it always
>>> avoids PLT (even if someone adds "-fplt" explicitly).
>> Do you mean that if cmodel=extreme,
>> then add -fno-plt by default?
> Yes, we should use -fno-plt as the default for cmodel=extreme.
>
> x86_64 silently ignores -fplt for cmodel=large (their "large" is like
> our "extreme"), but perhaps it's better for us to just report an error
> if someone uses "-mcmodel=extreme -fplt" explicitly (if possible, I'm
> not sure if we can determine whether -fplt is explicitly given in the
> backend code).
>
I thought if using -mcmodel=extreme and -fplt at the same time we could
add a warning here and inform the user that we changed to noplt.
prev parent reply other threads:[~2022-08-18 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 10:01 Lulu Cheng
2022-08-18 11:37 ` Xi Ruoyao
2022-08-18 11:49 ` Lulu Cheng
2022-08-18 12:52 ` Xi Ruoyao
2022-08-18 13:00 ` Lulu Cheng [this message]
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=524ce281-032e-4988-13c5-da8377d4246a@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xry111@xry111.site \
--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).