From: Xi Ruoyao <xry111@xry111.site>
To: Lulu Cheng <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH v1] LoongArch: Added code generation support for call36 function calls.
Date: Tue, 14 Nov 2023 17:55:23 +0800 [thread overview]
Message-ID: <4030bb00a356a8e8bb801f92951d444117d4dba0.camel@xry111.site> (raw)
In-Reply-To: <20231114094500.8160-1-chenglulu@loongson.cn>
On Tue, 2023-11-14 at 17:45 +0800, Lulu Cheng wrote:
> + /* When function calls are made through call36, t0 register will be
> + implicitly modified, so '-fno-ipa-ra' needs to be set here. */
> case CMODEL_MEDIUM:
> + if (HAVE_AS_SUPPORT_CALL36)
> + opts->x_flag_ipa_ra = 0;
> + break;
Maybe we can add a (clobber (reg:P 12)) to the related insns instead?
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-11-14 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 9:45 Lulu Cheng
2023-11-14 9:55 ` Xi Ruoyao [this message]
2023-11-14 12:46 ` chenglulu
2023-11-14 20:26 ` Xi Ruoyao
2023-11-14 20:42 ` Xi Ruoyao
2023-11-14 20:46 ` 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=4030bb00a356a8e8bb801f92951d444117d4dba0.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).