public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xicojovor at dropjar dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100432] New: gcc arm compilation binary output is bigger with -Os than -O2 Date: Wed, 05 May 2021 12:18:32 +0000 [thread overview] Message-ID: <bug-100432-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100432 Bug ID: 100432 Summary: gcc arm compilation binary output is bigger with -Os than -O2 Product: gcc Version: 11.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: xicojovor at dropjar dot com Target Milestone: --- example: https://godbolt.org/z/rYxTPdTcd while compiling for ARM, gcc versions after 4 (>= 5) generate a redundant stack frame as can be seen in the attached example, while gcc version 4 generates correct code that is also minimal in size as requested (-Os). The code generation in newer gcc versions is strange even without thinking about the -Os flag, since the generated stack frame is not even used, and the whole 3 instructions (sub sp, str, add sp) are totally not needed (the variable on the stack is not used). also reported in https://bugs.launchpad.net/gcc-arm-embedded/+bug/1927055 (not sure where this should be reported)
next reply other threads:[~2021-05-05 12:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-05 12:18 xicojovor at dropjar dot com [this message] 2021-05-05 14:27 ` [Bug target/100432] " rearnsha at gcc dot gnu.org 2021-05-06 5:51 ` xicojovor at dropjar dot com 2022-01-05 10:37 ` pinskia at gcc dot gnu.org
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=bug-100432-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).