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 build/31557] New: [gdb/build, aarch64] amd64_linux_read_description was not declared in this scope
Date: Mon, 25 Mar 2024 19:11:30 +0000	[thread overview]
Message-ID: <bug-31557-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31557
           Summary: [gdb/build, aarch64] amd64_linux_read_description was
                    not declared in this scope
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On aarch64-linux, with current trunk I'm running into a build breaker:
...
/home/vries/gdb/src/gdb/amd64-linux-tdep.c:1595:10: error:
‘amd64_linux_read_description’ was not declared in this scope; did you mean
‘i386_linux_read_description’?
 1595 |   return amd64_linux_read_description (xcr0 & X86_XSTATE_ALL_MASK,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |          i386_linux_read_description
/home/vries/gdb/src/gdb/amd64-linux-tdep.c: In function ‘void
amd64_linux_init_abi(gdbarch_info, gdbarch*)’:
/home/vries/gdb/src/gdb/amd64-linux-tdep.c:1840:19: error:
‘amd64_linux_read_description’ was not declared in this scope; did you mean
‘i386_linux_read_description’?
 1840 |                   amd64_linux_read_description (X86_XSTATE_SSE_MASK,
false));
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                   i386_linux_read_description
/home/vries/gdb/src/gdb/amd64-linux-tdep.c: In function ‘void
amd64_x32_linux_init_abi(g\
dbarch_info, gdbarch*)’:
/home/vries/gdb/src/gdb/amd64-linux-tdep.c:2054:23: error:
‘amd64_linux_read_description\
’ was not declared in this scope; did you mean ‘i386_linux_read_description’?
...

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

             reply	other threads:[~2024-03-25 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 19:11 vries at gcc dot gnu.org [this message]
2024-03-25 19:11 ` [Bug build/31557] " vries at gcc dot gnu.org
2024-03-25 23:02 ` mark at klomp dot org
2024-03-26 15:32 ` tromey at sourceware dot org
2024-03-26 16:51 ` tromey at sourceware dot org
2024-03-27  5: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-31557-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).