From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [rfc] [2/6] Remove macro TARGET_BYTE_ORDER
Date: Thu, 31 May 2007 21:03:00 -0000 [thread overview]
Message-ID: <200705312100.l4VL0VN9007416@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <465F2F73.2030407@de.ibm.com> from "Markus Deuling" at May 31, 2007 10:26:27 PM
Markus Deuling wrote:
> it seems that the TARGET_BYTE_ORDER patch was missing some pieces, so that not all
> appearance of it were replaced. So here is "the rest" of the patch. I run gdb_mbuild.sh
> and let it build all targets. They were build cleanly. Sorry for the inconvenience.
Sorry, I didn't notice this either when committing that patch. Thanks for the fix!
> * xtensa-tdep.c (XTENSA_IS_ENTRY,extract_call_winsize)
> (xtensa_register_write_masked,xtensa_register_read_masked)
> (xtensa_extract_return_value,xtensa_store_return_value
> (xtensa_push_dummy_call,xtensa_breakpoint_from_pc): Replace
> TARGET_BYTE_ORDER by gdbarch_byte_order.
> * sh-tdep.c (sh_breakpoint_from_pc,gdb_print_insn_sh)
> (sh_justify_value_in_reg,sh_next_flt_argreg,sh_push_dummy_call_fpu)
> (sh_extract_return_value_fpu,sh_store_return_value_fpu): Likewise.
> * sh64-tdep.c (sh64_breakpoint_from_pc,gdb_print_insn_sh64)
> (sh64_push_dummy_call,sh64_extract_return_value)
> (sh64_store_return_value,sh64_register_convert_to_virtual)
> (sh64_register_convert_to_raw,sh64_pseudo_register_read)
> (sh64_pseudo_register_write,sh64_do_fp_register)
> (sh64_frame_prev_register): Likewise.
> * score-tdep.c (score_print_insn,score_breakpoint_from_pc)
> (score_return_value,score_push_dummy_call,score_fetch_inst): Likewise.
> * rs6000-tdep.c (rs6000_breakpoint_from_pc,rs6000_push_dummy_call)
> (e500_move_ev_register,gdb_print_insn_powerpc): Likewise.
> * remote-m32r-sdi.c (m32r_resume,m32r_wait): Likewise.
> * ppc-linux-nat.c (store_register): Likewise.
> * nto-tdep.c (nto_find_and_open_solib)
> (nto_init_solib_absolute_prefix): Likewise.
> * mips-tdep.c (mips_pseudo_register_read,mips_pseudo_register_write)
> (mips_convert_register_p,mips_eabi_push_dummy_call)
> (mips_n32n64_push_dummy_call,mips_n32n64_return_value)
> (mips_o32_push_dummy_call,mips_o32_return_value)
> (mips_o64_push_dummy_call,mips_o64_return_value,mips_o64_return_value)
> (mips_read_fp_register_single,mips_read_fp_register_double)
> (mips_print_register,print_gp_register_row,gdb_print_insn_mips)
> (mips_breakpoint_from_pc): Likewise.
> * mipsnbsd-tdep.c (mipsnbsd_sigtramp_offset): Likewise.
> * mips-linux-tdep.c (mips64_supply_fpregset,mips64_fill_fpregset)
> (mips_linux_o32_sigframe_init): Likewise.
> * m32r-tdep.c (m32r_memory_insert_breakpoint)
> (m32r_memory_remove_breakpoint,m32r_breakpoint_from_pc): Likewise.
> * libunwind-frame.c (libunwind_frame_cache,libunwind_frame_sniffer)
> (libunwind_sigtramp_frame_sniffer,libunwind_get_reg_special): Likewise.
> * iq2000-tdep.c (iq2000_breakpoint_from_pc): Likewise.
> * coffread.c (process_coff_symbol): Likewise.
> * arm-tdep.c (convert_from_extended,convert_to_extended)
> (gdb_print_insn_arm): Likewise.
You should have a space after each comma. Also, this line:
> diff -urN src/gdb/mips-linux-tdep.c dev/gdb/mips-linux-tdep.c
> --- src/gdb/mips-linux-tdep.c 2007-05-31 19:31:37.000000000 +0200
> +++ dev/gdb/mips-linux-tdep.c 2007-05-31 21:09:14.000000000 +0200
> @@ -852,7 +854,7 @@
> layout, since we can't tell, and it's much more common. Which bits are
> the "high" bits depends on endianness. */
> for (ireg = 0; ireg < 32; ireg++)
> - if ((TARGET_BYTE_ORDER == BFD_ENDIAN_BIG) != (ireg & 1))
> + if (gdarch_byte_order (current_gdbarch) == BFD_ENDIAN_BIG) != (ireg & 1)
needs to read:
if ((gdbarch_byte_order (current_gdbarch) == BFD_ENDIAN_BIG) != (ireg & 1))
The rest looks OK, I've committed the patch with those two changes now.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-05-31 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 21:00 Markus Deuling
2007-05-31 21:03 ` Ulrich Weigand [this message]
2007-05-31 21:07 ` Markus Deuling
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 7:22 Markus Deuling
2007-05-30 21:19 ` Jim Blandy
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=200705312100.l4VL0VN9007416@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@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