public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/26950] New: FAIL: gdb.arch/amd64-disp-step-avx.exp: vex2: continue to test_rip_vex2_end
Date: Thu, 26 Nov 2020 12:20:21 +0000	[thread overview]
Message-ID: <bug-26950-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26950

            Bug ID: 26950
           Summary: FAIL: gdb.arch/amd64-disp-step-avx.exp: vex2: continue
                    to test_rip_vex2_end
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I'm running into:
...
[displaced] displaced_step_restore: restored process 115981 0x400182^M
^M
Program received signal SIGILL, Illegal instruction.^M
test_rip_vex2 () at
/tmp/tdevries/src/gdb/testsuite/gdb.arch/amd64-disp-step-avx.S:40^M
40              vmovsd ro_var(%rip),%xmm0^M
(gdb) FAIL: gdb.arch/amd64-disp-step-avx.exp: vex2: continue to
test_rip_vex2_end
...

The thing being tested here is vex encoding, which is an avx feature:
...
/* Test a VEX2-encoded RIP-relative instruction.  */

        .global test_rip_vex2
test_rip_vex2:
        vmovsd ro_var(%rip),%xmm0
        .global test_rip_vex2
test_rip_vex2_end:
        nop

...

The cpu has no avx support:
...
$ cat /proc/cpuinfo  | grep flags
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm
dca sse4_1 sse4_2 x2apic popcnt lahf_lm dtherm rsb_ctxsw retpoline kaiser
tpr_shadow vnmi flexpriority ept vpid
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-11-26 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 12:20 vries at gcc dot gnu.org [this message]
2020-11-27  8:47 ` [Bug testsuite/26950] " vries at gcc dot gnu.org
2021-09-04  8:44 ` cvs-commit at gcc dot gnu.org
2021-09-04 10:11 ` cvs-commit at gcc dot gnu.org
2021-09-04 10:12 ` vries 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-26950-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).