public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/110946] 3x perf regression with -Os on M1 Pro Date: Tue, 08 Aug 2023 12:22:56 +0000 [thread overview] Message-ID: <bug-110946-4-W24oQ7wRMG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110946-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110946 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> --- So basically missed inlining at -Os, even memcpy wrappers are not inlined. Can you provide a reproducible testcase? Note that inline functions in mbedtls/library/alignment.h all miss the 'static' qualifier, which affects inlining decisions, and looks like a mistake anyway (if they are really meant to be non-static inlines, shouldn't there be a comment?) Does making them 'static inline' rectify the problem?
next prev parent reply other threads:[~2023-08-08 12:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-08 11:25 [Bug other/110946] New: " dave.rodgman at arm dot com 2023-08-08 11:37 ` [Bug other/110946] " dave.rodgman at arm dot com 2023-08-08 12:22 ` amonakov at gcc dot gnu.org [this message] 2023-08-08 12:32 ` [Bug ipa/110946] " rguenth at gcc dot gnu.org 2023-08-08 12:35 ` [Bug other/110946] " dave.rodgman at arm dot com 2023-08-08 12:40 ` dave.rodgman at arm dot com 2023-08-08 13:27 ` dave.rodgman at arm dot com 2023-08-08 15:57 ` pinskia at gcc dot gnu.org 2023-08-08 16:48 ` [Bug ipa/110946] " amonakov at gcc dot gnu.org 2023-08-08 17:38 ` amonakov at gcc dot gnu.org 2023-08-08 21:20 ` amonakov at gcc dot gnu.org 2023-08-08 21:47 ` amonakov 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-110946-4-W24oQ7wRMG@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).