From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64826 invoked by alias); 20 Jul 2018 10:33:20 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 64787 invoked by uid 89); 20 Jul 2018 10:33:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=HOME, UD:gnu.gdb.i386.avx512, Topley, AVX-512 X-HELO: mail-wr1-f47.google.com Received: from mail-wr1-f47.google.com (HELO mail-wr1-f47.google.com) (209.85.221.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Jul 2018 10:33:18 +0000 Received: by mail-wr1-f47.google.com with SMTP id h10-v6so10831984wre.6 for ; Fri, 20 Jul 2018 03:33:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/RQcBc34yUXgSUS/Ml4qCzNrNgynHE9o6fkiLt3poL0=; b=M8mz45gW9l0JzSYFHbtR95PR4plBtciT0q9PNa3fytdBIXYjcHudwyQcdI1YwlgE5W 1eg4kyX3h9OrqHB0bORJXeKP1TRa9ONndCmgH8P3m27LYVcNSwsh9AXylaiNEOt5FTYH V/jTXKfGG3aAkcNTk7lwpkmWp4MVOkbb+P8240q/qlKDfvXibHDO9+OuDroGJXkqRtZj eLiJDm0RtFmFK9Kt6r3TxKhgakvWwbFslzd1LPBOxbLMgMrG6YwJXI4quBPpv8upiF/J WbVh8uNwu0kzvTHHmBYreIDJNT+PRuCsl+UzFESNFpRpzP5L16nWDJX4Nr+oCDNXA2Lt 5vcw== MIME-Version: 1.0 Received: by 2002:a1c:2c89:0:0:0:0:0 with HTTP; Fri, 20 Jul 2018 03:33:15 -0700 (PDT) In-Reply-To: References: From: Ruslan Kabatsayev Date: Fri, 20 Jul 2018 10:33:00 -0000 Message-ID: Subject: Re: ymm register error To: Paul Topley Cc: "gdb@sourceware.org" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-07/txt/msg00036.txt.bz2 Hi, On 17/07/2018, Paul Topley 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