public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28444] gdb fails to build on ppc64le when building with -flto
Date: Thu, 07 May 2026 19:39:43 +0000 [thread overview]
Message-ID: <bug-28444-4717-gGhEM1ZK95@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28444-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28444
Keith Seitz <keiths at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |keiths at redhat dot com
Resolution|DUPLICATE |---
Status|RESOLVED |REOPENED
--- Comment #3 from Keith Seitz <keiths at redhat dot com> ---
This appears to have popped up again
(FSF master updated May 6, 2026):
CXXLD gdbserver
../../src/gdbserver/../gdb/arch/ppc-linux-tdesc.h:46:29: error:
‘tdesc_powerpc_isa207_htm_vsx64l’ violates the C++ One Definition Rule
[-Werror=odr]
46 | extern const_target_desc_up tdesc_powerpc_isa207_htm_vsx64l;
| ^
powerpc-isa207-htm-vsx64l-generated.cc:26:27: note:
‘tdesc_powerpc_isa207_htm_vsx64l’ was previously declared here
26 | const struct target_desc *tdesc_powerpc_isa207_htm_vsx64l;
| ^
powerpc-isa207-htm-vsx64l-generated.cc:26:27: note: code may be misoptimized
unless ‘-fno-strict-aliasing’ is used
[snip]
I'm working on a patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2026-05-07 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 20:24 [Bug gdb/28444] New: " ahajkova at redhat dot com
2022-03-06 17:10 ` [Bug gdb/28444] " tromey at sourceware dot org
2023-09-11 7:35 ` vries at gcc dot gnu.org
2026-05-07 19:39 ` keiths at redhat dot com [this message]
2026-05-07 19:40 ` keiths at redhat dot com
2026-07-07 19:49 ` cvs-commit at gcc dot gnu.org
2026-07-07 19:50 ` keiths at redhat dot com
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-28444-4717-gGhEM1ZK95@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).