From: Xi Ruoyao <xry111@xry111.site>
To: WANG Xuerui <i@xen0n.name>, Lulu Cheng <chenglulu@loongson.cn>,
gcc-patches@gcc.gnu.org
Cc: xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: document -m[no-]explicit-relocs
Date: Wed, 27 Jul 2022 21:18:42 +0800 [thread overview]
Message-ID: <1935acaa28ba0c64418e549d89baca4d4d5b77bc.camel@xry111.site> (raw)
In-Reply-To: <4378ce76-7322-eb8d-fb10-41b3a59c9f7b@xen0n.name>
On Wed, 2022-07-27 at 17:57 +0800, WANG Xuerui wrote:
> On 2022/7/27 17:28, Lulu Cheng wrote:
> >
> >
> > 在 2022/7/27 下午5:15, Xi Ruoyao 写道:
> > > On Wed, 2022-07-27 at 16:47 +0800, Lulu Cheng wrote:
> > >
> > > > > "Use or do not use assembler relocation operators when dealing with
> > > > > symbolic addresses. The alternative is to use assembler macros
> > > > > instead, which may limit optimization.
> > > > >
> > > > > The default value for the option is determined during GCC build-
> > > > > time by detecting corresponding assembler support: @code{-mexplicit-
> > > > > relocs} if said support is present, @code{-mno-explicit-relocs}
> > > > > otherwise. This option is mostly useful for debugging, or
> > > > > interoperation with assemblers different from the build-time one."
> > > > >
> > > > I agree with wangxuerui's idea.
> > > > The same parameter and the same description information can reduce the
> > > > user's time to learn how to use this parameter.
> > > I agree it's better than my origin paragraph.
> > >
> > > If you agree I'll commit it with Xuerui as the commit author.
> > >
> >
> > I have no opinion if wangxuerui agrees.
> Either is OK (if you really think the commit is effectively rewritten by
> me), thanks.
Pushed r13-1859.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-07-27 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 7:06 Xi Ruoyao
2022-07-27 7:21 ` WANG Xuerui
2022-07-27 8:47 ` Lulu Cheng
2022-07-27 9:15 ` Xi Ruoyao
2022-07-27 9:28 ` Lulu Cheng
2022-07-27 9:57 ` WANG Xuerui
2022-07-27 13:18 ` Xi Ruoyao [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=1935acaa28ba0c64418e549d89baca4d4d5b77bc.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).