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/99881] Regression compare -O2 -ftree-vectorize with -O2 on SKX/CLX Date: Wed, 28 Jul 2021 22:47:16 +0000 [thread overview] Message-ID: <bug-99881-4-WiUV3xewfp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99881-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99881 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The testcase is buggy: Executing on host: /home/jakub/src/gcc/obj19/gcc/xgcc -B/home/jakub/src/gcc/obj19/gcc/ /home/jakub/src/gcc/gcc/testsuite/gcc.target/i386/pr99881.c -fdiagnostics-plain-output -Ofa st -march=skylake -ffat-lto-objects -fno-ident -S -o pr99881.s (timeout = 300) spawn -ignore SIGHUP /home/jakub/src/gcc/obj19/gcc/xgcc -B/home/jakub/src/gcc/obj19/gcc/ /home/jakub/src/gcc/gcc/testsuite/gcc.target/i386/pr99881.c -fdiagnostics-plain-output -Ofast -march=skylake -ffat-lto-objects -fno-ident -S -o pr99881.s PASS: gcc.target/i386/pr99881.c (test for excess errors) ERROR: (DejaGnu) proc "0-9" does not exist. The error code is TCL LOOKUP COMMAND 0-9 The info on the error is: invalid command name "0-9" while executing "::tcl_unknown 0-9" ("uplevel" body line 1) invoked from within "uplevel 1 ::tcl_unknown $args" xmm[0-9] should be xmm\[0-9]
next prev parent reply other threads:[~2021-07-28 22:47 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-02 3:49 [Bug target/99881] New: " crazylht at gmail dot com 2021-04-02 14:29 ` [Bug target/99881] " hjl.tools at gmail dot com 2021-04-02 19:34 ` hjl.tools at gmail dot com 2021-04-06 7:48 ` rguenth at gcc dot gnu.org 2021-04-06 10:06 ` crazylht at gmail dot com 2021-04-06 11:44 ` rguenth at gcc dot gnu.org 2021-07-28 2:48 ` cvs-commit at gcc dot gnu.org 2021-07-28 2:49 ` crazylht at gmail dot com 2021-07-28 22:47 ` jakub at gcc dot gnu.org [this message] 2021-07-29 1:09 ` crazylht at gmail dot com 2021-07-29 2:18 ` cvs-commit at gcc dot gnu.org 2021-08-19 2:32 ` crazylht at gmail dot com 2022-02-22 7:59 ` cvs-commit at gcc dot gnu.org 2022-02-22 8:00 ` rguenth 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-99881-4-WiUV3xewfp@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).