public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/96858] New: Many i386 testcases failed with different configured gcc on different hosts.
Date: Mon, 31 Aug 2020 05:52:17 +0000 [thread overview]
Message-ID: <bug-96858-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96858
Bug ID: 96858
Summary: Many i386 testcases failed with different configured
gcc on different hosts.
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: crazylht at gmail dot com
CC: hjl.tools at gmail dot com
Target Milestone: ---
Created attachment 49158
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49158&action=edit
compare_tests result for default arch -march=skylake-avx512 vs -march=x86-64 on
i386 backend testcases
For gcc version 11.0.0 20200831 (experimental) (GCC)
If gcc is built with default config, there's no unexpected failures for all
i386 backend testcases.
but when gcc is built with --with-arch=skylake-avx512, there would be lots of
unexpected failures
---
Tests that now fail, but worked before (469 tests):
---
It would be nice to adjust those testcases as we have regression tests for i386
backend with different gcc config.
next reply other threads:[~2020-08-31 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 5:52 crazylht at gmail dot com [this message]
2021-03-24 8:32 ` [Bug target/96858] " crazylht 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-96858-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: link
Be 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).