public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rachel Sapir <rachel@agito.co.il>
To: gcc-help@gcc.gnu.org
Cc: "Rachel Sapir" <rachel@akribis-sys.com>,
	"רחל דויטש" <rachel@agito.co.il>
Subject: Variables assigned to ram are increasing elf file size (=> occupying flash)
Date: Tue, 1 Sep 2020 13:21:34 +0300	[thread overview]
Message-ID: <CAMR5J=pdUCVBb92-HBoi3s6qprTOUSwOxOFU9R6SJ5trCnXYag@mail.gmail.com> (raw)

Hello,

I noticed that when I increase array sizes (I have some very big arrays)
the .elf file is increased by the same size. Since the elf file is saved to
the flash, it occupies flash area unnecessarily.

Is there a way to prevent this from happening?

Best regards,
Rachel

             reply	other threads:[~2020-09-01 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 10:21 Rachel Sapir [this message]
2020-09-01 15:41 ` Dan Kegel
     [not found]   ` <SL2PR01MB2795251A84A086E463F26FCE992F0@SL2PR01MB2795.apcprd01.prod.exchangelabs.com>
2020-09-02 14:19     ` Dan Kegel
2020-09-02 15:19   ` David Brown

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='CAMR5J=pdUCVBb92-HBoi3s6qprTOUSwOxOFU9R6SJ5trCnXYag@mail.gmail.com' \
    --to=rachel@agito.co.il \
    --cc=gcc-help@gcc.gnu.org \
    --cc=rachel@akribis-sys.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).