Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>
Subject: [patch] Use disassemble_info to get at the endianness
Date: Mon, 19 May 2008 15:17:00 -0000	[thread overview]
Message-ID: <4830FDF7.3060403@de.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

Hi,

this patch gets rid of another current_gdbarch by getting the endianess information from
disassemble_info in score-tdep.

Ok ?

ChangeLog:

	* score-tdep.c (score_print_insn): Get the current endianness from
	disassemble_info instead of gdbarch_byte_order.

Regards,
Markus

-- 
  Markus Deuling
  GNU Toolchain for Linux on Cell BE
  deuling@de.ibm.com


[-- Attachment #2: diff-score --]
[-- Type: text/plain, Size: 531 bytes --]

diff -urpN src/gdb/score-tdep.c dev/gdb/score-tdep.c
--- src/gdb/score-tdep.c	2008-04-24 05:51:39.000000000 +0200
+++ dev/gdb/score-tdep.c	2008-05-16 08:20:49.000000000 +0200
@@ -314,7 +314,7 @@ score_register_sim_regno (struct gdbarch
 static int
 score_print_insn (bfd_vma memaddr, struct disassemble_info *info)
 {
-  if (gdbarch_byte_order (current_gdbarch) == BFD_ENDIAN_BIG)
+  if (info->endian == BFD_ENDIAN_BIG)
     return print_insn_big_score (memaddr, info);
   else
     return print_insn_little_score (memaddr, info);

             reply	other threads:[~2008-05-19  4:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 15:17 Markus Deuling [this message]
2008-05-20 16:56 ` [patch] Use disassemble_info to get@the endianness Ulrich Weigand
2008-05-21 15:17   ` Markus Deuling

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=4830FDF7.3060403@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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