public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "markus.t.metzger at intel dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30751] [gdb/build] ODR violation for struct btrace_target_info
Date: Wed, 06 Sep 2023 07:18:36 +0000 [thread overview]
Message-ID: <bug-30751-4717-GOp0XoFvNi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30751-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30751
--- Comment #9 from Markus Metzger <markus.t.metzger at intel dot com> ---
(In reply to Tom de Vries from comment #8)
> (In reply to Markus Metzger from comment #4)
> > After configuring, I build GDB with:
> >
> > $ make -sj$(nproc) CFLAGS='-O2 -flto -Wall' CXXFLAGS='-O2 -flto -Wall'
> >
> > and I get several fails, e.g.
> >
> > .../sim/m32r/traps.c:115:43: error: type of 'm32r2f_h_psw_get' does not
> > match original declaration [-Werror=lto-type-mismatch]
> > 115 | m32r2f_h_bpsw_set (current_cpu, m32r2f_h_psw_get
> > (current_cpu));
> >
> > but no -Wodr warnings nor any other warnings related to btrace.
>
> I think what may be happening is that if you're getting an error while
> building sim, gdb is not build at all, because all-gdb requires
> maybe-all-sim.
>
> In that case, you could try building with --disable-sim.
After disabling sim, I get
bfd/elf32-xtensa.c:5725:41: error: 'MEM[(struct removal_by_action_entry
*)ientry_91 + -24B].offset' may be used uninitialized
[-Werror=maybe-uninitialized]
5725 | if (ctx->map.n_entries && (ientry - 1)->offset == r->offset)
|
but when I build with 'make -k' I can now reproduce the error and confirm that
it is fixed with my patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-06 7:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:27 [Bug build/30751] New: " vries at gcc dot gnu.org
2023-08-14 9:28 ` [Bug build/30751] " vries at gcc dot gnu.org
2023-08-14 9:35 ` sam at gentoo dot org
2023-08-14 12:36 ` tromey at sourceware dot org
2023-08-14 12:56 ` vries at gcc dot gnu.org
2023-08-14 13:20 ` markus.t.metzger at intel dot com
2023-08-14 18:03 ` tromey at sourceware dot org
2023-08-18 10:07 ` markus.t.metzger at intel dot com
2023-08-18 14:12 ` tromey at sourceware dot org
2023-08-18 14:29 ` vries at gcc dot gnu.org
2023-08-18 15:56 ` vries at gcc dot gnu.org
2023-08-21 6:55 ` vries at gcc dot gnu.org
2023-09-06 7:18 ` markus.t.metzger at intel dot com [this message]
2023-09-11 6:18 ` cvs-commit at gcc dot gnu.org
2023-09-11 6:55 ` 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-30751-4717-GOp0XoFvNi@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).