From: Alan Modra <amodra@bigpond.net.au>
To: gdb-patches@sources.redhat.com
Subject: Unreviewed patch
Date: Wed, 11 Sep 2002 01:45:00 -0000 [thread overview]
Message-ID: <20020911181503.U8357@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <20020829123940.J18764@bubble.sa.bigpond.net.au>; from amodra@bigpond.net.au on Thu, Aug 29, 2002 at 12:39:40PM +0930
I had a gdb patch buried in
http://sources.redhat.com/ml/gdb-patches/2002-08/msg00964.html
but apparently it was buried too deeply.
Here's a revised version, that also removes the silly bfd_lookup_arch
call.
gdb/ChangeLog
* x86-64-tdep.c (_initialize_x86_64_tdep): Don't use hard-coded
mach constants.
It's almost obvious, but I'm asking for permission to apply..
Index: gdb/x86-64-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/x86-64-tdep.c,v
retrieving revision 1.26
diff -u -p -r1.26 x86-64-tdep.c
--- gdb/x86-64-tdep.c 24 Aug 2002 00:21:35 -0000 1.26
+++ gdb/x86-64-tdep.c 29 Aug 2002 02:49:08 -0000
@@ -1144,7 +1144,7 @@ _initialize_x86_64_tdep (void)
}
tm_print_insn = gdb_print_insn_x86_64;
- tm_print_insn_info.mach = bfd_lookup_arch (bfd_arch_i386, 3)->mach;
+ tm_print_insn_info.mach = bfd_mach_x86_64;
/* Add the variable that controls the disassembly flavour. */
{
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2002-09-11 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFDCB00E28.6E375794-ON85256C23.005724F9@torolab.ibm.com>
[not found] ` <20020829092527.I18764@bubble.sa.bigpond.net.au>
2002-08-28 20:24 ` Latest 64-bit linker problem Alan Modra
2002-09-11 1:45 ` Alan Modra [this message]
2002-09-11 9:06 ` Unreviewed patch Kevin Buettner
2002-09-11 9:15 ` Michal Ludvig
2002-09-11 10:07 ` Kevin Buettner
2004-08-06 0:43 Ulrich Weigand
2004-08-11 19:10 ` Michael Snyder
2004-08-11 19:12 ` Daniel Jacobowitz
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=20020911181503.U8357@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=gdb-patches@sources.redhat.com \
/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