From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: cole945@gmail.com (Wei-cheng Wang)
Cc: brobecker@adacore.com (Joel Brobecker), gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3 v4] Process record support for PowerPC
Date: Mon, 19 Jan 2015 18:05:00 -0000 [thread overview]
Message-ID: <201501191804.t0JI4uSm024611@d03av02.boulder.ibm.com> (raw)
In-Reply-To: <54BD2C4B.7010102@gmail.com> from "Wei-cheng Wang" at Jan 20, 2015 12:09:47 AM
Wei-cheng Wang wrote:
> 2015-01-18 Wei-cheng Wang <cole945@gmail.com>
>
> * rs6000-tdep.c (ppc_process_record_op4, ppc_process_record_op19,
> ppc_process_record_op31, ppc_process_record_op59,
> ppc_process_record_op60, ppc_process_record_op63,
> ppc_process_record): Fix -Wformat warning.
> * rs6000-tdep.c (rs6000_epilogue_frame_cache, ppc_process_record_op60):
> Remove unused variables.
This is OK. Please check this in to fix the reported build issues.
> 2015-01-18 Wei-cheng Wang <cole945@gmail.com>
>
> * ppc-linux-tdep.c (ppc_skip_trampoline_code,
> ppc_canonicalize_syscall, ppc_linux_syscall_record,
> ppc_linux_record_signal, ppc_init_linux_record_tdep): Add comments.
> * ppc64-tdep.c (ppc64_skip_trampoline_code): Likewise.
> * rs6000-tdep.c (rs6000_epilogue_frame_cache,
> rs6000_epilogue_frame_this_id, rs6000_epilogue_frame_prev_register,
> rs6000_epilogue_frame_sniffer, ppc_record_vsr, ppc_process_record_op4,
> ppc_process_record_op19, ppc_process_record_op31,
> ppc_process_record_op59, ppc_process_record_op60,
> ppc_process_record_op63): Likewise.
A couple of minor issues:
> +/* Record registers which might be clobbered during system call.
> + Return 0 if succeed. */
I think proper English usage would be "Return 0 on success." or
"Return 0 if sucessful." (Here and elsewhere in the patch.)
> -/* Initialize linux_record_tdep if not initialized yet. */
> +/* Initialize linux_record_tdep if not initialized yet.
> + WORDSIZE is 4 or 8 for 32- or 64-bit PowerPC Linux respectively.
> + Sizes of data structures are initilzied accordingly. */
Typo "initilzied".
Otherwise, this is OK as well.
Two other things as an aside:
- When committing a patch to git, please add the ChangeLog to the
git commit message as well. Have a look with "git log" at the
existing practice how to format the commit messages for GDB.
- Given that you've now got commit access, please also add your name
to the MAINTAINERS file under "Write After Approval"; see here for
a recent example:
https://sourceware.org/ml/gdb-patches/2015-01/msg00517.html
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2015-01-19 18:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 18:00 [PATCH 2/3 v2] " Wei-cheng Wang
2014-12-08 19:12 ` Ulrich Weigand
2014-12-17 17:07 ` [PATCH 2/3 v3] " Wei-cheng Wang
2014-12-17 18:41 ` Ulrich Weigand
2014-12-25 17:27 ` [PATCH 2/3 v4] " Wei-cheng Wang
2015-01-01 14:19 ` Ulrich Weigand
2015-01-04 16:27 ` Wei-cheng Wang
2015-01-06 12:42 ` Ulrich Weigand
2015-01-17 6:02 ` Wei-cheng Wang
2015-01-17 11:47 ` Ulrich Weigand
2015-01-17 18:53 ` Joel Brobecker
2015-01-17 21:20 ` Broken build: rs6000-tdep.c: 32-bit host --enable-targets=all --enable-64-bit-bfd [Re: [PATCH 2/3 v4] Process record support for PowerPC] Jan Kratochvil
2015-01-18 4:47 ` Wei-cheng Wang
2015-01-18 7:01 ` Jan Kratochvil
2015-01-18 8:01 ` Wei-cheng Wang
2015-01-19 7:48 ` Joel Brobecker
2015-01-19 16:10 ` [PATCH 2/3 v4] Process record support for PowerPC Wei-cheng Wang
2015-01-19 18:05 ` Ulrich Weigand [this message]
2015-01-20 16:03 ` Wei-cheng Wang
2015-01-20 18:14 ` Ulrich Weigand
2015-01-26 17:19 ` Ulrich Weigand
2015-01-26 17:19 ` Wei-cheng Wang
2015-01-26 19:16 ` Doug Evans
2015-01-26 20:29 ` Doug Evans
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=201501191804.t0JI4uSm024611@d03av02.boulder.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=cole945@gmail.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