public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4250] LoongArch: doc: Update -m[no-]explicit-relocs for r14-4160 Date: Mon, 25 Sep 2023 08:29:10 +0000 (GMT) [thread overview] Message-ID: <20230925082910.3B6F53858C2A@sourceware.org> (raw) https://gcc.gnu.org/g:c25d6f152118ebf680bf9f5ece98278e5ae13d9d commit r14-4250-gc25d6f152118ebf680bf9f5ece98278e5ae13d9d Author: Xi Ruoyao <xry111@xry111.site> Date: Mon Sep 25 16:10:58 2023 +0800 LoongArch: doc: Update -m[no-]explicit-relocs for r14-4160 gcc/ChangeLog: * doc/invoke.texi: Update -m[no-]explicit-relocs for r14-4160. Diff: --- 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.
reply other threads:[~2023-09-25 8:29 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230925082910.3B6F53858C2A@sourceware.org \ --to=xry111@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).