public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "admin at levyhsu dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106315] New: 7.8% increased codesize on specfp 507.cactuBSSN_r Date: Fri, 15 Jul 2022 14:55:06 +0000 [thread overview] Message-ID: <bug-106315-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106315 Bug ID: 106315 Summary: 7.8% increased codesize on specfp 507.cactuBSSN_r Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: admin at levyhsu dot com Target Milestone: --- when compiled with march_native_ofast_lto (-march=native -Ofast -funroll-loops -flto) on IceLake,CascadeLake, SkylakeW, Zen3 Server/Client, r13-1268-g8c99e307b20c50 results 7.8%-7.9% codesize increment. On aarch64 codesize looks ok.
next reply other threads:[~2022-07-15 14:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-15 14:55 admin at levyhsu dot com [this message] 2022-07-18 7:34 ` [Bug tree-optimization/106315] [13 Regression] " rguenth at gcc dot gnu.org 2022-07-18 8:50 ` marxin at gcc dot gnu.org 2022-07-21 3:26 ` admin at levyhsu dot com 2022-07-21 15:28 ` hjl.tools at gmail dot com 2022-07-25 6:30 ` admin at levyhsu dot com 2022-07-29 14:48 ` hjl.tools at gmail dot com 2023-02-21 14:05 ` rguenth at gcc dot gnu.org 2023-04-26 6:56 ` [Bug tree-optimization/106315] [13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2024-03-09 17:16 ` law at gcc dot gnu.org 2024-05-21 9:11 ` [Bug tree-optimization/106315] [13/14/15 " jakub 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-106315-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).