From: Markus Deuling <deuling@de.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [rfc] [2/6] Remove macro TARGET_BYTE_ORDER
Date: Thu, 31 May 2007 21:07:00 -0000 [thread overview]
Message-ID: <465F37CA.1020708@de.ibm.com> (raw)
In-Reply-To: <200705312100.l4VL0VN9007416@d12av02.megacenter.de.ibm.com>
Ulrich Weigand wrote:
> 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)
<..>
>> * 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.
>
Thank you very much.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next prev parent reply other threads:[~2007-05-31 21:03 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
2007-05-31 21:07 ` Markus Deuling [this message]
-- 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=465F37CA.1020708@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