public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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] LoongArch: doc: Update -m[no-]explicit-relocs for r14-4160
Date: Mon, 25 Sep 2023 16:29:35 +0800	[thread overview]
Message-ID: <44398f09dd45df8058ec8ace3ac8c4532b86635f.camel@xry111.site> (raw)
In-Reply-To: <33a96b18-3108-48a8-2b55-206a9c469144@loongson.cn>

On Mon, 2023-09-25 at 16:26 +0800, chenglulu wrote:
> LGTM!
> 
> Thank you for your modification!

Pushed r14-4250.

> 在 2023/9/25 下午4:13, Xi Ruoyao 写道:
> > gcc/ChangeLog:
> > 
> > 	* doc/invoke.texi: Update -m[no-]explicit-relocs for r14-4160.
> > ---
> > 
> > I've not regtested this as it's only a doc change.  Ok for trunk?
> > 
> >   gcc/doc/invoke.texi | 10 ++++++----
> >   1 file changed, 6 insertions(+), 4 deletions(-)
> > 
> > diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> > index ba7984bcb7e..146b40414b0 100644
> > --- a/gcc/doc/invoke.texi
> > +++ b/gcc/doc/invoke.texi
> > @@ -26159,10 +26159,12 @@ The default code model is @code{normal}.
> >   @itemx -mno-explicit-relocs
> >   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
> > +limit instruction scheduling but allow linker relaxation.  The default
> > +value for the option is determined during GCC build-time by detecting
> > +corresponding assembler support:
> > +@code{-mno-explicit-relocs} if the assembler supports relaxation or it
> > +does not support relocation operators at all,
> > +@code{-mexplicit-relocs} otherwise.  This option is mostly useful for
> >   debugging, or interoperation with assemblers different from the build-time
> >   one.
> >   
> 

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2023-09-25  8:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  8:13 Xi Ruoyao
2023-09-25  8:26 ` chenglulu
2023-09-25  8:29   ` 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=44398f09dd45df8058ec8ace3ac8c4532b86635f.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).