public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake) Date: Fri, 11 Sep 2020 06:31:14 +0000 [thread overview] Message-ID: <bug-97018-4-HaL5yVUB4w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97018-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0 Last reconfirmed| |2020-09-11 Ever confirmed|0 |1 Summary|[r11 Regression] FAIL: |[11 Regression] FAIL: |gcc.target/i386/l_fma_float |gcc.target/i386/l_fma_float |_1.c scan-assembler-times |_1.c scan-assembler-times |vfnmsub[123]+ss 32 on |vfnmsub[123]+ss 32 on |Linux/x86_64 (-m64 |Linux/x86_64 (-m64 |-march=cascadelake) |-march=cascadelake) Status|UNCONFIRMED |WAITING Target| |x86_64-*-* i?86-*-* --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Do they PASS on the GCC 10 branch?
next prev parent reply other threads:[~2020-09-11 6:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-11 6:11 [Bug regression/97018] New: [r11 " skpgkp2 at gmail dot com 2020-09-11 6:31 ` rguenth at gcc dot gnu.org [this message] 2020-09-11 7:12 ` [Bug target/97018] [11 " crazylht at gmail dot com 2020-09-11 16:52 ` cvs-commit at gcc dot gnu.org 2020-09-11 16:53 ` hjl.tools at gmail dot com 2020-09-11 17:07 ` skpgkp2 at gmail dot com 2020-09-11 17:20 ` hjl.tools at gmail dot com 2020-09-11 18:14 ` hjl.tools at gmail 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-97018-4-HaL5yVUB4w@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).