public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@sc.intel.com>
To: skpgkp2@gmail.com, hjl.tools@gmail.com, gcc-regression@gcc.gnu.org
Subject: Regressions under Intel SDE on native/master at commit r13-2870 vs commit r13-2841 on Linux/x86_64
Date: Mon, 26 Sep 2022 08:57:17 -0700	[thread overview]
Message-ID: <20220926155717.99C463E001E@gnu-clx-1.sc.intel.com> (raw)

New failures:

New passes:
FAIL: gcc.target/i386/avx256-unaligned-store-3.c scan-assembler vextractf128
FAIL: gcc.target/i386/avx256-unaligned-store-3.c scan-assembler vextractf128
FAIL: gcc.target/i386/avx256-unaligned-store-3.c scan-assembler vmovupd.*movv2df_internal/4
FAIL: gcc.target/i386/avx256-unaligned-store-3.c scan-assembler vmovupd.*movv2df_internal/4

To reproduce the test failures:

$ cd gcc
$ make check RUNTESTFLAGS="--target_board='unix{-m32,}' i386.exp=failed-test"

If a run-time test failure fails to reproduce, please run the executable
under Intel SDE which can be downloaded from

https://www.intel.com/content/www/us/en/developer/articles/tool/software-development-emulator.html

$ ..../sde -future -- ./executable

To debug executable under SDE:

1. Turn on SDE debug:

$ ..../sde -future -debug -- ./executable

and you should get:

Application stopped until continued from debugger.
Start GDB, then issue this command at the (gdb) prompt:
  target remote :xxxxx

where xxxxx is a random number.

2. Run gdb

$ gdb ./executable
...
(gdb) target remote :xxxxx

and you should get:
...
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
0x00007fae0fc07100 in _start ()
   from /lib64/ld-linux-x86-64.so.2
(gdb)

                 reply	other threads:[~2022-09-26 15:57 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=20220926155717.99C463E001E@gnu-clx-1.sc.intel.com \
    --to=hjl@sc.intel.com \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=skpgkp2@gmail.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).