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/105643] New: [13 Regression] Code-Size regression for specrate 538.imagick_r Date: Wed, 18 May 2022 09:06:14 +0000 [thread overview] Message-ID: <bug-105643-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105643 Bug ID: 105643 Summary: [13 Regression] Code-Size regression for specrate 538.imagick_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: --- We found on Intel platform, commit r13-128-g938a02a589dc22 (938a02a589dc22cef65bba2b131fc9e4874baddb) results 53.7% codesize increment when compiled with march_native_ofast_lto(-march=native -Ofast -funroll-loops -flto) for specrate 538.imagick_r on SkylakeW, Cascade Lake and IceLake. On Zen3 Server/Client code size looks alright.
next reply other threads:[~2022-05-18 9:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-18 9:06 admin at levyhsu dot com [this message] 2022-05-18 10:03 ` [Bug tree-optimization/105643] " pinskia at gcc dot gnu.org 2022-05-18 12:47 ` rguenth at gcc dot gnu.org 2022-05-18 13:15 ` marxin at gcc dot gnu.org 2022-05-19 3:46 ` admin at levyhsu dot com 2022-05-19 8:51 ` admin at levyhsu dot com 2022-05-19 8:52 ` admin at levyhsu dot com 2022-05-19 9:11 ` admin at levyhsu dot com 2022-05-19 10:31 ` rguenth at gcc dot gnu.org 2022-05-31 3:56 ` crazylht at gmail dot com 2022-06-01 7:50 ` rguenther at suse dot de 2022-10-19 10:11 ` rguenth 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-105643-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).