public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110059] When SPEC is used to test the GCC (10.3.1), the test result of subitem 548 fluctuates abnormally. Date: Wed, 31 May 2023 13:54:43 +0000 [thread overview] Message-ID: <bug-110059-4-XkKTiiRftF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110059-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110059 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I'd like to point out that doing performance testing for GCC 10 at this point isn't a very good idea, GCC 10 is going out of support within a month or two, and while some important wrong-code generation bugs can be still fixed there, it is very unlikely any performance related bugs would be fixed there. Of course, if you find a performance problem with GCC 13 or even better trunk compared to GCC 9 or older and then bisect it to a particular change, it is helpful.
next prev parent reply other threads:[~2023-05-31 13:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 11:43 [Bug target/110059] New: " d_vampile at 163 dot com 2023-05-31 12:14 ` [Bug target/110059] " d_vampile at 163 dot com 2023-05-31 12:23 ` pinskia at gcc dot gnu.org 2023-05-31 13:42 ` ktkachov at gcc dot gnu.org 2023-05-31 13:54 ` jakub at gcc dot gnu.org [this message] 2023-06-02 7:30 ` rguenth at gcc dot gnu.org 2023-06-05 1:41 ` 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-110059-4-XkKTiiRftF@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).