public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103973] x86: 4-way comparison of floats/doubles with spaceship operator possibly suboptimal Date: Tue, 18 Jan 2022 03:17:32 +0000 [thread overview] Message-ID: <bug-103973-4-3ajNjU6SJ9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103973-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103973 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:5e26bf17220926d308d0e3bb82bae6e592d2e485 commit r12-6655-g5e26bf17220926d308d0e3bb82bae6e592d2e485 Author: liuhongt <hongtao.liu@intel.com> Date: Tue Jan 18 10:45:10 2022 +0800 Adjust testcase for --target_board='unix{-m64\ -march=cascadelake}' Change scan-assembler from "\tucomisd" to "\t\[v\]?ucomisd". gcc/testsuite/ChangeLog: PR target/103973 * g++.target/i386/pr103973-1.C: Change scan-assembler from "\tucomisd" to "\t\[v\]?ucomisd". * g++.target/i386/pr103973-11.C: Ditto. * g++.target/i386/pr103973-13.C: Ditto. * g++.target/i386/pr103973-15.C: Ditto. * g++.target/i386/pr103973-3.C: Ditto. * g++.target/i386/pr103973-5.C: Ditto. * g++.target/i386/pr103973-7.C: Ditto. * g++.target/i386/pr103973-9.C: Ditto. * gcc.target/i386/pr103973-1.c: Ditto. * gcc.target/i386/pr103973-11.c: Ditto. * gcc.target/i386/pr103973-13.c: Ditto. * gcc.target/i386/pr103973-15.c: Ditto. * gcc.target/i386/pr103973-3.c: Ditto. * gcc.target/i386/pr103973-5.c: Ditto. * gcc.target/i386/pr103973-7.c: Ditto. * gcc.target/i386/pr103973-9.c: Ditto.
prev parent reply other threads:[~2022-01-18 3:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 3:54 [Bug target/103973] New: " nekotekina at gmail dot com 2022-01-11 4:47 ` [Bug target/103973] " crazylht at gmail dot com 2022-01-11 4:49 ` crazylht at gmail dot com 2022-01-11 4:55 ` pinskia at gcc dot gnu.org 2022-01-11 5:09 ` nekotekina at gmail dot com 2022-01-11 8:52 ` rguenth at gcc dot gnu.org 2022-01-11 19:34 ` jakub at gcc dot gnu.org 2022-01-11 19:46 ` jakub at gcc dot gnu.org 2022-01-14 20:13 ` jakub at gcc dot gnu.org 2022-01-17 12:41 ` cvs-commit at gcc dot gnu.org 2022-01-17 16:41 ` jakub at gcc dot gnu.org 2022-01-18 3:17 ` cvs-commit at gcc dot gnu.org [this message]
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-103973-4-3ajNjU6SJ9@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).