public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d_vampile at 163 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111332] New: Using GCC7.3.0 and GCC10.3.0 to compile the same test case, assembler file instructions are different and performance fallback is obvious. Date: Fri, 08 Sep 2023 01:49:31 +0000 [thread overview] Message-ID: <bug-111332-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111332 Bug ID: 111332 Summary: Using GCC7.3.0 and GCC10.3.0 to compile the same test case, assembler file instructions are different and performance fallback is obvious. Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: d_vampile at 163 dot com Target Milestone: --- Created attachment 55850 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55850&action=edit test case Created Attachment Test platform: x86_64 Compiler Options: gcc main.c -g -o main -O2 -msse4.2 -mavx2 -fno-inline Runtime with gcc7.3.0: $ time ./main_gcc7.3 2000 start to run 2000. end to run 2000. real 6m30.461s user 6m26.587s sys 0m0.814s Runtime with gcc10.3.0: $ time ./main_gcc10.3 2000 start to run 2000. end to run 2000. real 7m18.696s user 7m13.912s sys 0m1.098s Programs compiled with gcc10.3.0 run significantly longer than gcc7.3.0
next reply other threads:[~2023-09-08 1:49 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-08 1:49 d_vampile at 163 dot com [this message] 2023-09-08 1:54 ` [Bug target/111332] " d_vampile at 163 dot com 2023-09-08 1:58 ` d_vampile at 163 dot com 2023-09-08 2:11 ` pinskia at gcc dot gnu.org 2023-09-08 2:16 ` pinskia at gcc dot gnu.org 2023-09-08 2:34 ` d_vampile at 163 dot com 2023-09-08 2:38 ` d_vampile at 163 dot com 2023-09-08 2:40 ` d_vampile at 163 dot com 2023-09-08 4:00 ` pinskia at gcc dot gnu.org 2023-09-08 4:09 ` d_vampile at 163 dot com
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-111332-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).