Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Paul Topley <paul.topley@calnexsol.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: ymm register error
Date: Fri, 20 Jul 2018 10:33:00 -0000	[thread overview]
Message-ID: <CAHEcG95Heoo1Fso5JNzn7-xGr=KvbxNAERTW5SPXc4HNvZrfWA@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0501MB23733695073ADC48984C9F96E55C0@DB6PR0501MB2373.eurprd05.prod.outlook.com>

Hi,

On 17/07/2018, Paul Topley <paul.topley@calnexsol.com> wrote:
> When trying to run gdb server on a skylake-x HEDT platform (i9-7940X) I
> encounter the following error:
>
>
> regcache.c:264: A problem internal to GDBserver has been detected.
> Unknown register ymm0h requested

How exactly do you run it to get this error?

>
> From what I can tell from furious googling is that the ymm registers have
> changed location from broadwell-e to skylake-x.

Broadwell-E doesn't support AVX-512, while Skylake-X does. This might
be the difference, but on Bochs with AVX-512 and XSAVE support enabled
I failed to reproduce your problem. I tried to do it by running
gdbserver from git master on /bin/true and then attaching from another
VT and trying `info all-reg` command. Also `p $ymm0h` and `info reg
ymm0h` commands do succeed for me (as does `info reg zmm0`, which
confirms that AVX-512 support is working).

>
> I can see references to the ymm registers in gdb's codebase, with apparent
> positioning related to features like org.gnu.gdb.i386.avx &
> org.gnu.gdb.i386.avx512.
>
> Being a complete novice around gdb's codebase, I'm not sure if I need to
> enable or state something at configure stage so that the right ymm register
> location is referenced.
>
> gdb server 8 in ubuntu bionics repos works OK on the skylake-x platform, but
> when I compile myself it does not.
>
> Is there something specific I need to be stating at compile time to "get"
> gdbserver 8 to work on skylake-x

I simply configured gdb via `configure --prefix=$HOME/opt/gdb-git`,
without any additional options, and it works as described above. Could
you check that latest git master still has the problem?

>
> Paul
>
>

Regards,
Ruslan


      parent reply	other threads:[~2018-07-20 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 11:44 Paul Topley
2018-07-17 15:08 ` Simon Marchi
2018-07-20 10:33 ` Ruslan Kabatsayev [this message]

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='CAHEcG95Heoo1Fso5JNzn7-xGr=KvbxNAERTW5SPXc4HNvZrfWA@mail.gmail.com' \
    --to=b7.10110111@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=paul.topley@calnexsol.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