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 python/29712] [gdb, aarch64] UNRESOLVED: gdb.python/py-disasm.exp: global_disassembler=ReadMemoryGdbErrorDisassembler: disassemble test
Date: Fri, 21 Oct 2022 14:18:43 +0000 [thread overview]
Message-ID: <bug-29712-4717-BhgrfNx1o0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29712-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29712
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> Maybe -fexceptions missing on the opcodes file or some such.
Yep, this patch is sufficient to make the test-case pass on aarch64:
...
diff --git a/opcodes/Makefile.in b/opcodes/Makefile.in
index fe4539d6097..03efe198461 100644
--- a/opcodes/Makefile.in
+++ b/opcodes/Makefile.in
@@ -206,11 +206,11 @@ depcomp = $(SHELL) $(top_srcdir)/../depcomp
am__depfiles_maybe = depfiles
am__mv = mv -f
COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
- $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
+ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -fexceptions
LTCOMPILE = $(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) \
$(LIBTOOLFLAGS) --mode=compile $(CC) $(DEFS) \
$(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) \
- $(AM_CFLAGS) $(CFLAGS)
+ $(AM_CFLAGS) $(CFLAGS) -fexceptions
AM_V_CC = $(am__v_CC_@AM_V@)
am__v_CC_ = $(am__v_CC_@AM_DEFAULT_V@)
am__v_CC_0 = @echo " CC " $@;
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-21 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 10:47 [Bug python/29712] New: " vries at gcc dot gnu.org
2022-10-21 13:09 ` [Bug python/29712] " vries at gcc dot gnu.org
2022-10-21 13:43 ` vries at gcc dot gnu.org
2022-10-21 14:11 ` vries at gcc dot gnu.org
2022-10-21 14:18 ` vries at gcc dot gnu.org [this message]
2022-10-21 20:54 ` aburgess at redhat dot com
2022-10-22 4:31 ` vries at gcc dot gnu.org
2022-10-24 9:17 ` vries at gcc dot gnu.org
2022-10-24 12:51 ` aburgess at redhat dot com
2022-10-31 18:17 ` brobecker at gnat dot com
2022-11-02 7:12 ` luis.machado at arm dot com
2022-11-28 19:24 ` cvs-commit at gcc dot gnu.org
2022-11-28 19:24 ` cvs-commit at gcc dot gnu.org
2022-12-01 18:10 ` tromey at sourceware dot org
2022-12-02 16:39 ` aburgess 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-29712-4717-BhgrfNx1o0@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).