public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dmitry.neverov at jetbrains dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31532] gdb/gmp-utils.c:169: internal-error: export_bits: Assertion `word_countp == 1' failed.
Date: Sat, 23 Mar 2024 15:47:53 +0000	[thread overview]
Message-ID: <bug-31532-4717-mZTosbLale@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31532-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Dmitry Neverov <dmitry.neverov at jetbrains dot com> ---
Turns out it was gmp build problem. Gmp was build without an
explicit --build option, and it guessed it to
be "skylake-pc-linux-gnu". In this configuration gmp uses LZCNT
instruction. When gdb was launched on a CPU without LZCNT
support, the BSR instruction is executed instead. BSR produces a
different result from LZCNT which triggers the assertion. That's
why same gdb build was working fine on some (newer) machines, but
failed on others. Building gmp with --build=x86_64-pc-linux-gnu
fixes the problem.

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

  parent reply	other threads:[~2024-03-23 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 15:30 [Bug gdb/31532] New: " dmitry.neverov at jetbrains dot com
2024-03-22 15:49 ` [Bug gdb/31532] " vries at gcc dot gnu.org
2024-03-22 16:14 ` tromey at sourceware dot org
2024-03-22 19:31 ` dmitry.neverov at jetbrains dot com
2024-03-23 15:47 ` dmitry.neverov at jetbrains dot com [this message]
2024-03-23 18:49 ` tromey at sourceware dot 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-31532-4717-mZTosbLale@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).