From: Gabriele Favalessa <gabriele@rzerosystems.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ARM: code size increase starting from gcc 10
Date: Mon, 14 Mar 2022 11:05:58 +0100 [thread overview]
Message-ID: <CAGRyuqywbSq=zE_iUXi0cu19naMqJsdHRvLbdG0cKEbCBn0jMA@mail.gmail.com> (raw)
In-Reply-To: <43782800-80df-c4ce-9379-c4bb3c6c60a4@foss.arm.com>
On Fri, Mar 11, 2022 at 4:20 PM Richard Earnshaw <
Richard.Earnshaw@foss.arm.com> wrote:
> > 1) why newer gcc versions don't generate the smallest possible size in
> > spite of -Os?
>
> The compiler is trying to identify opportunities to generate even better
> code for more common cases.
>
> > 2) is there a way to get the smaller code with newer gcc versions?
>
> Unfortunately, no. At least not at present.
Thanks, the info you provided was very helpful in understanding my options.
Gabriele
prev parent reply other threads:[~2022-03-14 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 9:57 Gabriele Favalessa
2022-03-11 15:20 ` Richard Earnshaw
2022-03-14 10:05 ` Gabriele Favalessa [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='CAGRyuqywbSq=zE_iUXi0cu19naMqJsdHRvLbdG0cKEbCBn0jMA@mail.gmail.com' \
--to=gabriele@rzerosystems.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc-help@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: 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).