public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lin1.hu at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115462] [15 regression] 416.gamess regressed 4-6% on x86_64 since r15-882-g1d6199e5f8c1c0 Date: Thu, 20 Jun 2024 06:35:13 +0000 [thread overview] Message-ID: <bug-115462-4-cQKdlExvBP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115462-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115462 --- Comment #4 from Hu Lin <lin1.hu at intel dot com> --- Created attachment 58470 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58470&action=edit A short case I tested the file with 1) -Ofast -flto -march=skylake-avx512 -mfpmath=sse -funroll-loops 2) -O2 -march=native (on an Icelake server) Both generate redundant mov.
next prev parent reply other threads:[~2024-06-20 6:35 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-12 15:04 [Bug target/115462] New: " jamborm at gcc dot gnu.org 2024-06-13 7:24 ` [Bug target/115462] [15 regression] " rguenth at gcc dot gnu.org 2024-06-13 9:09 ` liuhongt at gcc dot gnu.org 2024-06-20 2:00 ` lin1.hu at intel dot com 2024-06-20 6:35 ` lin1.hu at intel dot com [this message] 2024-06-27 6:14 ` cvs-commit at gcc dot gnu.org 2024-06-27 6:15 ` liuhongt 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-115462-4-cQKdlExvBP@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).