From: Andrew Cagney <ac131313@redhat.com>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] revised m32r target
Date: Sun, 27 Jul 2003 16:24:00 -0000 [thread overview]
Message-ID: <3F23FCC9.9040908@redhat.com> (raw)
In-Reply-To: <01fc01c3500e$7800d2f0$5169910a@KEI>
> Kei,
>>
>> I've checked in the .c files, as posted. Not bad, not bad at all.
>> Can you just see how many of the attached can also be fixed? I'll then
>> look at enabling it and pulling it into the 6 branch.
>>
>> Andrew
>
>
> Thank you for checking in. I revised m32r-tdep.c and m32r-rom.c.
> I think all warnings in your e-mail are fixed now. I attached the
> patch file.
>
> By the way, would you tell me how to get these warning messages?
I ran the script: "gdb_ari.sh -Wari <file>". See:
http://sources.redhat.com/gdb/current/ari/
http://sources.redhat.com/gdb/current/ari/gdb_ari.sh
> I built gdb with --enable-build-warnings, but gcc didn't show them.
Can you try configuring/building with:
--enable-gdb-build-warnings=,-Werror
(all targets should configure/build with that) I'm seeing the warnings:
m32r-tdep.c: In function `m32r_store_return_value':
m32r-tdep.c:289: warning: pointer of type `void *' used in arithmetic
m32r-rom.c: In function `m32r_upload_command':
m32r-rom.c:466: warning: `hostent' might be used uninitialized in this
function
Can you please try to reproduce / fix this.
BTW, for the ChangeLog I checked in:
2003-07-27 Andrew Cagney <cagney@redhat.com>
Patch from 2003-07-22 Kei Sakamoto <sakamoto.kei@renesas.com>:
* m32r-tdep.c (m32r_memory_insert_breakpoint): Fix code style -
operator at start and not end of line.
(decode_prologue): Ditto.
(m32r_frame_unwind_cache, m32r_unwind_sp, m32r_unwind_pc): Use
frame_unwind_register_unsigned instead of
frame_unwind_unsigned_register.
(m32r_read_pc): Use regcache_cooked_read_unsigned instead of
read_register.
(m32r_push_dummy_call): Use register_size instead of
REGISTER_RAW_SIZE.
(m32r_frame_sniffer): Replace m32r_frame_p.
(m32r_gdbarch_init): Call frame_unwind_append_sniffer.
* m32r-rom.c (report_transfer_performance): Delete extern
declaration.
(m32r_load, m32r_upload_command): Use print_transfer_performance
instead of report_transfer_performance.
(_initialize_m32r_rom): Use add_setshow_cmd instead of add_set_cmd
/ add_show_from_set.
as it better states what was changed.
Andrew
next prev parent reply other threads:[~2003-07-27 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 2:00 Kei Sakamoto
2003-07-11 7:15 ` Kei Sakamoto
2003-07-11 13:31 ` Andrew Cagney
2003-07-21 18:49 ` Andrew Cagney
2003-07-22 5:00 ` Kei Sakamoto
2003-07-27 16:24 ` Andrew Cagney [this message]
2003-07-28 6:45 ` Kei Sakamoto
2003-08-01 21:12 ` Andrew Cagney
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=3F23FCC9.9040908@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=sakamoto.kei@renesas.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