public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: haochen.jiang@intel.com, gcc-patches@gcc.gnu.org,
	gcc-regression@gcc.gnu.org, vmakarov@redhat.com
Subject: [r13-4727 Regression] FAIL: gcc.target/i386/pr64110.c scan-assembler vmovd[\\t ] on Linux/x86_64
Date: Sun, 18 Dec 2022 06:59:49 +0800	[thread overview]
Message-ID: <202212172259.2BHMxnm7145572@shliclel314.sh.intel.com> (raw)

On Linux/x86_64,

12abd5a7d13209f79664ea603b3f3517f71b8c4f is the first bad commit
commit 12abd5a7d13209f79664ea603b3f3517f71b8c4f
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Thu Dec 15 14:11:05 2022 -0500

    IRA: Check that reg classes contain a hard reg of given mode in reg move cost calculation

caused

FAIL: 20_util/to_chars/float16_c++23.cc execution test
FAIL: gcc.target/i386/pr64110.c scan-assembler vmovd[\\t ]

with GCC configured with

../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-4727/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=20_util/to_chars/float16_c++23.cc --target_board='unix{-m32}'"
$ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=20_util/to_chars/float16_c++23.cc --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr64110.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr64110.c --target_board='unix{-m32\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com)

                 reply	other threads:[~2022-12-17 23:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202212172259.2BHMxnm7145572@shliclel314.sh.intel.com \
    --to=haochenj@ecsmtp.sh.intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=vmakarov@redhat.com \
    /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).