public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wu yanan <corawu.yn@gmail.com>
To: Stefan Ring <stefanrin@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Does current gcc have segment compression option?
Date: Thu, 17 Nov 2022 18:20:17 +0800	[thread overview]
Message-ID: <CA+OPFbDkCTLHshq5g5dxj7Ba=wPirbnqbQza338=TQQ8Bjhvhw@mail.gmail.com> (raw)
In-Reply-To: <CAAxjCEyRpFmO-KKuFZ+RFEMhaGjaEt+Ubn51n4aRj=PviZXVpw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

Does there have options to use the  linker or loader runtime to compress  the
segments?

On Thu, Nov 17, 2022 at 5:56 PM Stefan Ring via Gcc-help <
gcc-help@gcc.gnu.org> wrote:

> On Wed, Nov 16, 2022 at 4:52 AM Wu yanan via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> >
> > When i find information about reduce execution size, i found that in
> > compilers like tiarmclang(
> >
> https://software-dl.ti.com/codegen/docs/tiarmclang/rel1_3_0_LTS/compiler_manual/linker_description/08_using_linker_generated_copy_tables/compression-stdz0754720.html
> )
> > and IAR,there are options provided to compress segments of
> > execution(data,text..etc). usually i use gcc and clang compiler, are
> there
> > similar options  to compress the  segments of execution? I only found
> > compress options for debug information in clang compiler.
>
> This looks like a feature by the linker and loader runtime and
> probably doesn’t have anything to do with the compiler.
>

      reply	other threads:[~2022-11-17 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  3:51 Wu yanan
2022-11-17  9:55 ` Stefan Ring
2022-11-17 10:20   ` Wu yanan [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='CA+OPFbDkCTLHshq5g5dxj7Ba=wPirbnqbQza338=TQQ8Bjhvhw@mail.gmail.com' \
    --to=corawu.yn@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=stefanrin@gmail.com \
    /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).